Changed 'optimize_max' for 'optimize' compile option on Chromium

The 'optimize_max' option is not meant to be used by default for Release builds. These use the 'optimize' config. See comment here for explanation: https://cs.chromium.org/chromium/src/build/config/compiler/BUILD.gn?l=1572 Change-Id: I7af8e3e4c7e92c60f38841b75998e2b488a5ffde Reviewed-on: https://swiftshader-review.googlesource.com/11228Reviewed-by: Alexis Hétu <sugoi@google.com> Tested-by: Alexis Hétu <sugoi@google.com>

Changed 'optimize_max' for 'optimize' compile option on Chromium
aadf3e13 · Alexis Hetu · Alexis Hétu · 84d0e223 · aadf3e13
Commit aadf3e13 authored Aug 03, 2017 by Alexis Hetu Committed by Alexis Hétu Aug 03, 2017
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

swiftshader.gni src/swiftshader.gni +1 -1

No files found.
--- a/src/swiftshader.gni
+++ b/src/swiftshader.gni
@@ -20,7 +20,7 @@ if (is_debug) {
  ]
  configs_to_add += [
    "//build/config:release",
-    "//build/config/compiler:optimize_max",
+    "//build/config/compiler:optimize",
  ]
  if (is_win) {
    configs_to_delete += [ "//build/config/win:default_crt" ]