History log of /frameworks/compile/slang/BitWriter_3_2/Android.mk
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
8f093e05e28046b6fc74175b66a06152f72e0c66 04-Mar-2016 Pirama Arumuga Nainar <pirama@google.com> Update slang for LLVM rebase to r256229

Bug: http://b/26987366

(cherry picked from commit 98cfae456bb1831336bce2b21979a04e2e31fed4)

Change-Id: Ic7f67da3fee0da075f11e3125132af7ea9c96457
/frameworks/compile/slang/BitWriter_3_2/Android.mk
c8b0cda5299441cf5793c940a248adfde8fb4255 19-Aug-2015 Dan Willemsen <dwillemsen@google.com> Stop checking HOST_OS, whitelist windows modules

Bug: 23566667
Change-Id: I048140d0fa740fb162653b3540d999d6097515fb
/frameworks/compile/slang/BitWriter_3_2/Android.mk
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_3_2/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_3_2/Android.mk
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