Descriptionninja windows: fix mapping of optimization flags
"FavorSizeOrSpeed" should map to Os/Ot. These were backwards.
"Optimization" can also be set to Disabled/Size/Speed/Max which maps to
Od/O1/O2/Ox. Seems a bit silly, but that's how VS exposes the compiler
settings. Previously, Size/Speed here were incorrectly duplicating the Os/Ot
setting rather than O1/O2.
So, before we were basically doing some random set of optimizing flags.
(I have no idea what the compiler actually attempts to do when you set O1+Ot
or O2+Os. I guess it must be macro vs. micro level, but it's not very clear
from the names. Chromium sets them consistently.)
R=thakis@chromium.org
BUG=126315
Committed: https://code.google.com/p/gyp/source/detail?r=1363
Patch Set 1 #Patch Set 2 : fix Os/Ot map #
Total comments: 2
Patch Set 3 : neither test, and reorder #
Messages
Total messages: 3 (0 generated)
|