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/11228
Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Alexis Hétu <sugoi@google.com>

diff --git a/src/swiftshader.gni b/src/swiftshader.gni
index c4292e3..253d405 100644 (file)
--- 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" ]