History log of /frameworks/compile/slang/BitWriter_3_2/Android.mk
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
6cd16fb4dc2466f9fdebb407ad7c42437d67976e 22-Jun-2013 Stephen Hines <srhines@google.com> Provide LLVM 3.2 BitcodeWriter as a device static library.

This will allow the bcinfo BitcodeTranslator to write LLVM 3.2
compatible bitcode.

Change-Id: Id0137ec04a102f09af5b4c0b8020c5ae9b9f3554
/frameworks/compile/slang/BitWriter_3_2/Android.mk
8bb06b7c40b14ce2dae414b0aa034e9b23b278c9 21-Jun-2013 Stephen Hines <srhines@google.com> Write legacy function attributes properly.

Bug: 9503142

A prior LLVM rebase accidentally overwrote the various bitcode writer
implementations with respect to function attributes. They were writing a new
style section, which would not be able to be parsed/used on older devices.
This change restores the generation of the legacy function attribute bitcode
format.

Change-Id: Ib6afc5ae405303881605c51c34b6966e4754c29d
/frameworks/compile/slang/BitWriter_3_2/Android.mk
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/Android.mk