[issue9225] Replace DUP_TOPX with DUP_TOP_TWO

2010-09-04 Thread Antoine Pitrou
Antoine Pitrou added the comment: Modified patch committed in r84501. Thanks! -- resolution: -> fixed stage: -> committed/rejected status: open -> closed type: performance -> resource usage ___ Python tracker ___

[issue9225] Replace DUP_TOPX with DUP_TOP_TWO

2010-07-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Oddly, at least with pybench, use of PREDICT(BINARY_SUBSCR) in > DUP_TOP_TWO seems to show an always right PREDICT as slower than > FAST_DISPATCH The main point of computed gotos is to allow the CPU's branch predictor to predict opcode pairs by itself. So, y

[issue9225] Replace DUP_TOPX with DUP_TOP_TWO

2010-07-11 Thread Demur Rumed
Changes by Demur Rumed : -- versions: +Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue9225] Replace DUP_TOPX with DUP_TOP_TWO

2010-07-11 Thread Demur Rumed
New submission from Demur Rumed : DUP_TOPX(3) is never used, nor is ROT_FOUR. This patch removes the opcodes, replacing DUP_TOPX with DUP_TOP_TWO Oddly, at least with pybench, use of PREDICT(BINARY_SUBSCR) in DUP_TOP_TWO seems to show an always right PREDICT as slower than FAST_DISPATCH -