[Python-Dev] Arena-freeing obmalloc ready for testing
Tim Peters
tim.peters at gmail.com
Thu Mar 2 18:27:17 CET 2006
More information about the Python-Dev mailing list
Thu Mar 2 18:27:17 CET 2006
- Previous message: [Python-Dev] Arena-freeing obmalloc ready for testing
- Next message: [Python-Dev] ref leak w/except hooks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Tim Peters] >> ... >> However, the new branch isn't predictable, so who knows? [Nick Craig-Wood] > When compiling with gcc at least you could give the compiler a hint, > eg > > http://kerneltrap.org/node/4705 By "the new branch isn't predictable", I mean that there's apparently no way to guess which way it's going to go that's better than flipping a coin. If I could annotate the branch with the probability of the branch being taken, my best guess would be "half the time". OTOH, if I rearranged the code a little, the new test could become highly predictable. OK, I'll do that :-) > ... > Excellent work! Thanks redirected to Evan, who worked hard for a long time on this. Thanks, Evan!
- Previous message: [Python-Dev] Arena-freeing obmalloc ready for testing
- Next message: [Python-Dev] ref leak w/except hooks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list