Message166964
| Author |
vstinner |
| 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日.07:10:46 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1343718647.52.0.371334222231.issue8847@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I noticed when building with VC++ 2010 Express on the PGI/PGO
> builds that it warns about PGO not being available.
Even if PGO is not available, wrap_binaryfunc() and wrap_binaryfunc_l() functions get the same address when Python is compiled in "PGUpdate" mode. (I tried Visual C++ 2010 Express).
The issue was seen at least with the following versions:
Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit (Intel)] on win32
Python 3.2 (which version exactly?)
Python 3.3b.01, MSVC v16.00 64 bits (AMD 64) on win32
So the issue was also reproduced with old Python versions compiled with Visual C++ 2008, and I'm not sure that the "ICF" optimization is only enabled in "Profile-Guided" (PG*) modes.
If we choose to change Visual Studio options instead of changing the mode, we may also try /Gy- option:
http://msdn.microsoft.com/en-us/library/xsa71f43.aspx |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年07月31日 07:10:47 | vstinner | set | recipients:
+ vstinner, loewis, georg.brandl, rhettinger, terry.reedy, ishimoto, amaury.forgeotdarc, ncoghlan, pitrou, jackdied, tim.golden, eric.araujo, mrabarnett, alex, r.david.murray, brian.curtin, skrah, meador.inge, benrg |
| 2012年07月31日 07:10:47 | vstinner | set | messageid: <1343718647.52.0.371334222231.issue8847@psf.upfronthosting.co.za> |
| 2012年07月31日 07:10:46 | vstinner | link | issue8847 messages |
| 2012年07月31日 07:10:46 | vstinner | create |
|