[ovs-dev] [PATCH 2/2] cccl: Enable compiler optimization by default.

Eitan Eliahu eliahue at vmware.com
Thu Aug 28 17:45:25 UTC 2014

Hi Guru, 
Do we distinguish between Debug and Releases builds? ( I recall we discussed this before but forgot what was the outcome)
Enabling optimization may cause some issues for the debugger to match the source to the code.

-----Original Message-----
From: dev [mailto:dev-bounces at openvswitch.org] On Behalf Of Gurucharan Shetty
Sent: Thursday, August 28, 2014 9:39 AM
To: dev at openvswitch.org
Cc: Gurucharan Shetty
Subject: [ovs-dev] [PATCH 2/2] cccl: Enable compiler optimization by default.

There is no 1-1 mapping between gcc's compiler optimization flags and MSVC's optimization flags making the automatic conversions trickier.

This commit adds the /O2 option which is the recommended option for fast code.

Signed-off-by: Gurucharan Shetty <gshetty at nicira.com>
 build-aux/cccl |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/build-aux/cccl b/build-aux/cccl index c18629a..eb4d2aa 100644
--- a/build-aux/cccl
+++ b/build-aux/cccl
@@ -45,7 +45,7 @@ esac
 # We'll assume cl to start out
 # opts specifies the command line to pass to the MSVC program -clopt="${slash}nologo ${slash}FS"
+clopt="${slash}nologo ${slash}FS ${slash}O2"
 # gotparam is 0 if we didn't ever see a param, in which case we show usage()  gotparam=

dev mailing list
dev at openvswitch.org

More information about the dev mailing list