| 6103e43f4fc7fcaa455b33b76dd8e636ab1425c8 |
|
11-Feb-2014 |
Stephen Hines <srhines@google.com> |
Update slang for LLVM 3.4 rebase.
Remove LinkOnceODRAutoHideLinkage, since it is now just a special case of
LinkOnceODRLinkage.
Remove CaseRange expansion code from all bitcode writers, since it is now dead.
Fix up HeaderSearch constructor.
Change-Id: I38547486be509b16ea5d8218b43c31ae35b37d3b
/frameworks/compile/slang/BitWriter_3_2/BitcodeWriterPass.cpp
|
| 99d429070eb7c4c39fb7d74555031d518a4e0a79 |
|
17-Dec-2013 |
Stephen Hines <srhines@google.com> |
Split up case-range in BitWriter_3_2 as well.
Bug: 12135682
This is a temporary WAR, as LLVM 3.4 removes support for case-range statements
completely. That is a much larger patch to external/llvm, and requires more
thorough testing.
Change-Id: Ief8ec4796a8cce13ffc8cb4f2b961eecdc7ca264
/frameworks/compile/slang/BitWriter_3_2/BitcodeWriterPass.cpp
|
| d711dec946b6408791ca59eb98e363ef04bbd4aa |
|
09-Jan-2013 |
Stephen Hines <srhines@google.com> |
Add BitWriter_3_2 for JB+ target API.
This change switches llvm-rs-cc to use a single format for JB+ target API
LLVM bitcode. This simplifies upstream rebases, considering the divergent
compressed bitcode format that will be present in LLVM 3.3. We may move
back to using the upstream BitWriter again at some point in the future, but
for now, it seems like the best choice is to stick with the 3.2 format.
Change-Id: I8cfc54d7da7c7168f8f0d5f8fc24c2598b81aff8
/frameworks/compile/slang/BitWriter_3_2/BitcodeWriterPass.cpp
|