aboutsummaryrefslogtreecommitdiffstats
path: root/BitWriter_3_2/Android.mk
Commit message (Collapse)AuthorAgeFilesLines
* Use gcc instead of clang when building Windows SDK.Logan Chien2014-06-131-0/+3
| | | | | | | | Also, we should use the libstdc++ from GCC toolchain instead of libc++ since gcc does not support _Atomic type yet. Change-Id: Ib901811278ed5cac2c5a64ef2d2cbdfa7c3a1081
* Use clang for llvm-related projectAndrew Hsieh2014-05-081-0/+1
| | | | | | | | clang/llvm 3.5 depends on libcxx's <atomic> which uses _Atomic not available in gcc until 4.9. Even then, the _Atomic support is in C11 mode, not C++11 mode. Change-Id: I211afa5a7ebaa4de88cbedcd44e70bf9e2bac879
* Provide LLVM 3.2 BitcodeWriter as a device static library.Stephen Hines2013-06-211-0/+18
| | | | | | | This will allow the bcinfo BitcodeTranslator to write LLVM 3.2 compatible bitcode. Change-Id: Id0137ec04a102f09af5b4c0b8020c5ae9b9f3554
* Write legacy function attributes properly.Stephen Hines2013-06-211-2/+3
| | | | | | | | | | | | 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
* Add BitWriter_3_2 for JB+ target API.Stephen Hines2013-01-081-0/+26
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-18 02:46:14 +0000