This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author blaisorblade
Recipients Ringding, ajaksu2, alexandre.vassalotti, bboissin, belopolsky, blaisorblade, christian.heimes, collinwinter, djc, facundobatista, gregory.p.smith, jyasskin, lemburg, pitrou, ralph.corderoy, rhettinger, skip.montanaro, spiv, theatrus
Date 2009-01-26.15:28:34
SpamBayes Score 7.497015e-06
Marked as misclassified No
Message-id <1232983715.55.0.906589769122.issue4753@psf.upfronthosting.co.za>
In-reply-to
Content
-fno-gcse is controversial.
Even if it might avoid jumps sharing, the impact of that option has to
be measured, since common subexpression elimination allows omitting some
recalculations, so disabling global CSE might have a negative impact on
other code.

It would be maybe better to disable GCSE only for the interpreter loop,
but that would make some intra-file inlining impossible.
History
Date User Action Args
2009-01-26 15:28:36blaisorbladesetrecipients: + blaisorblade, lemburg, skip.montanaro, collinwinter, rhettinger, facundobatista, gregory.p.smith, spiv, belopolsky, pitrou, christian.heimes, ajaksu2, alexandre.vassalotti, jyasskin, djc, ralph.corderoy, bboissin, theatrus, Ringding
2009-01-26 15:28:35blaisorbladesetmessageid: <1232983715.55.0.906589769122.issue4753@psf.upfronthosting.co.za>
2009-01-26 15:28:34blaisorbladelinkissue4753 messages
2009-01-26 15:28:34blaisorbladecreate