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 meador.inge
Recipients alex, amaury.forgeotdarc, benrg, brian.curtin, eric.araujo, georg.brandl, ishimoto, jackdied, loewis, meador.inge, mrabarnett, ncoghlan, pitrou, r.david.murray, rhettinger, skrah, terry.reedy, tim.golden, vstinner
Date 2012-07-31.01:36:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Nice work Victor.

> Can we turn that particular optimisation off?

/OPT:NOICF is probably what we are looking for [1]:

/OPT:ICF can result in the same address being assigned to different functions or read only data members (const variables compiled with /Gy). So, /OPT:ICF can break a program that depends on the address of functions or read-only data members being different. See /Gy (Enable Function-Level Linking) for more information.

Now it makes sense that this only crops up with the PGO builds -- those are the only ones where we link with /OPT:ICF.

Can someone try out this option?  I would, but I don't have a Windows box handy.

Date User Action Args
2012-07-31 01:36:04meador.ingesetrecipients: + meador.inge, loewis, georg.brandl, rhettinger, terry.reedy, ishimoto, amaury.forgeotdarc, ncoghlan, pitrou, vstinner, jackdied, tim.golden, eric.araujo, mrabarnett, alex, r.david.murray, brian.curtin, skrah, benrg
2012-07-31 01:36:04meador.ingesetmessageid: <>
2012-07-31 01:36:03meador.ingelinkissue8847 messages
2012-07-31 01:36:03meador.ingecreate