summaryrefslogtreecommitdiffstats
path: root/ui/ozone/platform
diff options
context:
space:
mode:
authorpcc <pcc@chromium.org>2015-04-15 15:21:07 -0700
committerCommit bot <commit-bot@chromium.org>2015-04-15 22:21:46 +0000
commit3a725956aff76414de8ecec2dcaa773b21fc8fe5 (patch)
tree893da83b5a8865294cbea326d580f56664954733 /ui/ozone/platform
parent553b419e9a4a9dc1eb0ac5845c04c1c99ba59e40 (diff)
downloadchromium_src-3a725956aff76414de8ecec2dcaa773b21fc8fe5.zip
chromium_src-3a725956aff76414de8ecec2dcaa773b21fc8fe5.tar.gz
chromium_src-3a725956aff76414de8ecec2dcaa773b21fc8fe5.tar.bz2
Misc undefined symbol fixes for Android+LTO.
It appears that at least in some cases, the linker uses a stricter set of rules when linking LTO objects, which causes the link to fail in some cases where an unused function depends on an undefined symbol. This change fixes all such cases where the error caused the LTO build to fail, by either moving source files between lists, or by selectively disabling parts of source files depending on the configuration. There are more errors like this, which for some reason do not affect LTO. They can be inspected like this (with a regular Chromium/android build): $ ninja -C out/Release chrome_shell_apk $ nm out/Release/lib/libchromeshell.so | grep " U _Z" BUG=407544 R=thakis@chromium.org Review URL: https://codereview.chromium.org/1086973003 Cr-Commit-Position: refs/heads/master@{#325325}
Diffstat (limited to 'ui/ozone/platform')
0 files changed, 0 insertions, 0 deletions