Stop passing -fomit-frame-pointers in swiftshader build file

The //build/config files have a whole song and dance about frame pointers in //build/config/compiler:default_stack_frames and //build/config/compiler/compiler.gni (enable_frame_pointers), so rely on that. This has the effect of enabling frame pointers in more configs, which happens to work around an lld/mac bug -- but this seems like a good change regardless. Bug: chromium:1220175 Change-Id: I59dbb80fce2c50db658c3cf0cb13690ced88cbfe Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55630Tested-by: 's avatarNico Weber <thakis@chromium.org> Reviewed-by: 's avatarNicolas Capens <nicolascapens@google.com> Reviewed-by: 's avatarAlexis Hétu <sugoi@google.com> Commit-Queue: Nico Weber <thakis@chromium.org>
parent 3a5f44ab
......@@ -53,10 +53,7 @@ config("swiftshader_config") {
[ "NO_SANITIZE_FUNCTION=__attribute__((no_sanitize(\"function\")))" ]
if (!is_debug) {
cflags += [
"-fomit-frame-pointer",
"-Os",
]
cflags += [ "-Os" ]
defines += [ "ANGLE_DISABLE_TRACE" ]
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment