diff options
| author | Jan Voung <jvoung@chromium.org> | 2013-09-13 11:09:47 -0700 |
|---|---|---|
| committer | Jan Voung <jvoung@chromium.org> | 2013-09-13 11:09:47 -0700 |
| commit | 156e8330e6df89812148f8e1b22cd883391deedc (patch) | |
| tree | 609efc84acfd9422d7645126800cf2b1e531569a /tools/pnacl-bcanalyzer | |
| parent | a90e7c5042db33b4cc05625af4593e1a796533dc (diff) | |
Localize the le32 -> ARM hack to the LTO module for bitcode linking.
Only the bitcode linker via gold / lto module cares about
le32 being a target w/ a real backend.
LTOModule/LTOCodeGenerator is interested in having a real
target to know the name mangling and assembly notation
conventions (e.g., what's the prefix for private symbols).
This removes the hack from the bitcode reader so that
tools like llvm-dis are not affected and nonfinal pexes can
still say that they are "le32".
This is still not pretty, but it's better than polluting
the BitcodeReader, especially if certain tools check
what llvm-dis returns, and this doesn't require making a
dummy backend just for name mangling and asm conventions.
BUG=https://code.google.com/p/nativeclient/issues/detail?id=2554
TEST= trybots
http://chromegw.corp.google.com/i/tryserver.nacl/builders/nacl-toolchain-linux-pnacl-x86_32/builds/826
http://chromegw.corp.google.com/i/tryserver.nacl/builders/nacl-toolchain-mac-pnacl-x86_32/builds/830
http://chromegw.corp.google.com/i/tryserver.nacl/builders/nacl-toolchain-linux-pnacl-x86_64/builds/876
R=dschuff@chromium.org
Review URL: https://codereview.chromium.org/23619038
Diffstat (limited to 'tools/pnacl-bcanalyzer')
0 files changed, 0 insertions, 0 deletions