MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004089CMakeCMakepublic2006-11-29 08:032016-06-10 14:30
ReporterJoseph 
Assigned ToBrad King 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0004089: Visual Studio generator doesn't handle custom optimizations
DescriptionI am trying to compile one of my targets with the following optimization flags:
"/Og /Oi /Ot /Oy /Ob2 /Gs /GF"
That's equivalent to "/O2 /Gy-", but I can't use /Gy- because it's only supported in VS2005 and because cmake doesn't parse it correctly.
Now it turns out I can't use that long sequence either, because the following happens:
1. As none of /Od, /O1, /O2, /Ox is present, the Optimization=x attribute is not put to a .vcproj file.
2. Visual Studio doesn't default to "Custom" optimization, but rather to "Maximize Speed", which causes /O2 to be used instead of my custom flags.

A patch is attached.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filesdiff cmLocalVisualStudio7Generator.diff (684) 1969-12-31 19:00
https://public.kitware.com/Bug/file/755/cmLocalVisualStudio7Generator.diff
Issue History
Date ModifiedUsernameFieldChange
2012-08-13 10:44Brad KingStatusassigned => backlog
2012-08-13 10:44Brad KingNote Added: 0030563
2016-06-10 14:27Kitware RobotNote Added: 0041334
2016-06-10 14:27Kitware RobotStatusbacklog => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:30Kitware RobotStatusresolved => closed

Notes
(0006516)
Bill Hoffman   
2007-02-21 14:03   
Will your new flag parsing stuff fix this?
(0006517)
Brad King   
2007-02-21 14:18   
No, but the same fix is easily ported to my new parser by writing a method similar to that FixExceptionHandlingDefault.
(0030563)
Brad King   
2012-08-13 10:44   
Sending issues I'm not actively working on to the backlog to await someone with time for them.

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it:

 http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer or contributor who has the bandwidth to take it on.
(0041334)
Kitware Robot   
2016-06-10 14:27   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.