Message328757
| Author | vstinner |
|---|---|
| Recipients | Aaron Hall, benjamin.peterson, mark.dickinson, miss-islington, serhiy.storchaka, thatiparthy, vstinner |
| Date | 2018-10-28.21:38:58 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1540762738.48.0.788709270274.issue35059@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> I would like to see Py_LOCAL_INLINE removed, too, fwiw. Oh. Why? Do you want to directly use "static" and "static inline"? I guess that Py_LOCAL and Py_LOCAL_INLINE have been added to use __fastcall with MSVC. ... __fastcall is mostly interesting in x86 (32-bit), but x86-64 calling convention is "fast" by default no? __fastcall pass the first two arguments in registers, but x86-64 already pass the first four arguments in registers... Do you mean that __fastcall is no longer revelant? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-10-28 21:38:58 | vstinner | set | recipients: + vstinner, mark.dickinson, benjamin.peterson, serhiy.storchaka, thatiparthy, Aaron Hall, miss-islington |
| 2018-10-28 21:38:58 | vstinner | set | messageid: <1540762738.48.0.788709270274.issue35059@psf.upfronthosting.co.za> |
| 2018-10-28 21:38:58 | vstinner | link | issue35059 messages |
| 2018-10-28 21:38:58 | vstinner | create | |