In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/688ea162f4a70352089e12b46feab20232234ccf?hp=0e27d581cb664f678ac5c3df263d85f7774efc69>
- Log ----------------------------------------------------------------- commit 688ea162f4a70352089e12b46feab20232234ccf Author: Daniel Dragan <[email protected]> Date: Thu Feb 21 08:42:13 2013 +0000 PATCH: [perl #116787] -Ox on Win64 Visual C 64 bit is flawed, switch to -O1 -Ox is missing -GF and -Gy and -Gs http://blogs.msdn.com/b/branbray/archive/2005/07/08/437078.aspx http://msdn.microsoft.com/en-us/library/8f8h5cxt%28v=vs.90%29.aspx http://msdn.microsoft.com/en-us/library/59a3b321%28v=vs.90%29.aspx So the remaining question is, use -O1 or use -O2 on VC 64? VC 32 bit uses -O1, and that is also slightly faster on x64 too. ----------------------------------------------------------------------- Summary of changes: win32/Makefile | 2 +- win32/makefile.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/win32/Makefile b/win32/Makefile index 221f096..7631eae 100644 --- a/win32/Makefile +++ b/win32/Makefile @@ -439,7 +439,7 @@ LINK_DBG = -debug -opt:ref,icf #LINK_DBG = $(LINK_DBG) -debugtype:both ! IF "$(WIN64)" == "define" # enable Whole Program Optimizations (WPO) and Link Time Code Generation (LTCG) -OPTIMIZE = $(OPTIMIZE) -Ox -GL +OPTIMIZE = $(OPTIMIZE) -O1 -GL LINK_DBG = $(LINK_DBG) -ltcg ! ELSE # -O1 yields smaller code, which turns out to be faster than -O2 on x86 diff --git a/win32/makefile.mk b/win32/makefile.mk index 2d396c0..8a196a6 100644 --- a/win32/makefile.mk +++ b/win32/makefile.mk @@ -503,7 +503,7 @@ LINK_DBG = -debug -opt:ref,icf #LINK_DBG = $(LINK_DBG) -debugtype:both .IF "$(WIN64)" == "define" # enable Whole Program Optimizations (WPO) and Link Time Code Generation (LTCG) -OPTIMIZE += -Ox -GL +OPTIMIZE += -O1 -GL LINK_DBG += -ltcg .ELSE # -O1 yields smaller code, which turns out to be faster than -O2 on x86 -- Perl5 Master Repository
