231f578e0b0c2467e1b71e3ba5cd035caf1a9d88 |
|
26-May-2014 |
Logan Chien <tzuhsiang.chien@gmail.com> |
Use gcc instead of clang when building Windows SDK. Also, we should use the libstdc++ from GCC toolchain instead of libc++ since gcc does not support _Atomic type yet. Change-Id: Ib901811278ed5cac2c5a64ef2d2cbdfa7c3a1081
/frameworks/compile/slang/BitWriter_2_9/Android.mk
|
19bb5f5a3fd5146956de28127b88089f3538a4cd |
|
08-May-2014 |
Andrew Hsieh <andrewhsieh@google.com> |
Use clang for llvm-related project 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
/frameworks/compile/slang/BitWriter_2_9/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_2_9/Android.mk
|
4cc499d6e5ec602309501873449c938af61170b2 |
|
25-Aug-2011 |
Stephen Hines <srhines@google.com> |
Start basic support for LLVM 2.9 bitcode writer. Change-Id: I6a54158a32e485f506f0b991f89125b8a0e60267
/frameworks/compile/slang/BitWriter_2_9/Android.mk
|