Message261700
| Author |
brett.cannon |
| Recipients |
benjamin.peterson, brett.cannon, georg.brandl, ncoghlan, yselivanov, ztane |
| Date |
2016年03月13日.17:36:44 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1457890604.98.0.835387413084.issue26549@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I also suspect you're right, Antti, that the stack size is calculated prior to the bytecode being passed to through the peepholer which would have made the built tuple a value in the const array.
Off the top of my head I don't remember where the stack size calculation is made, but my suspicion is it's in the AT -> bytecode step, which would mean making it work from bytecode would mean re-implementing that calculation to work from the bytecode itself (assuming I'm right). |
|