Message217798
| Author |
josh.r |
| Recipients |
josh.r, pitrou, vstinner |
| Date |
2014年05月02日.21:27:34 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1399066054.82.0.182500330097.issue21419@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
One possible way to salvage it: Have you considered declaring long_alloc as Py_LOCAL_INLINE, or, now that I've checked #5553, a macro for long_alloc, so it gets inlined, and doesn't add the check overhead to everything (since properly inlining with a constant argument to use_calloc should make the optimizer trim the unused code path at compile time)?
Probably not very PEP7 friendly to macro-ize something that long I'm guessing... |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年05月02日 21:27:34 | josh.r | set | recipients:
+ josh.r, pitrou, vstinner |
| 2014年05月02日 21:27:34 | josh.r | set | messageid: <1399066054.82.0.182500330097.issue21419@psf.upfronthosting.co.za> |
| 2014年05月02日 21:27:34 | josh.r | link | issue21419 messages |
| 2014年05月02日 21:27:34 | josh.r | create |
|