[Python-Dev] Split unicodeobject.c into subfiles
Nick Coghlan
ncoghlan at gmail.com
Thu Oct 25 13:11:18 CEST 2012
More information about the Python-Dev mailing list
Thu Oct 25 13:11:18 CEST 2012
- Previous message: [Python-Dev] Split unicodeobject.c into subfiles
- Next message: [Python-Dev] Split unicodeobject.c into subfiles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Oct 25, 2012 at 8:07 PM, Maciej Fijalkowski <fijall at gmail.com> wrote: >> >> I think you misunderstood. What I described is the reason for having >> the base codecs in unicodeobject.c. >> >> I think we all agree that inlining has a positive effect on >> performance. The scale of the effect depends on the used compiler >> and platform. >> > > Well. Inlining can have positive or negative effects, depending on > various details. Too much inlining causes more cache misses for > example. However, this is absolutely irrelevant if you don't create > benchmarks and run them. Guessing is seriously not a very good > optimization strategy. Yep, that's why I made the point that speed.python.org should be a going concern well before 3.4 release, and will be able to let us know if we have a problem relative to 3.3. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Split unicodeobject.c into subfiles
- Next message: [Python-Dev] Split unicodeobject.c into subfiles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list