History log of /frameworks/compile/slang/BitWriter_3_2/ValueEnumerator.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
2444eaadc5a5197e2c3192afd74c38e9e4bb0ffe 06-May-2015 Pirama Arumuga Nainar <pirama@google.com> Update slang for rebase to LLVM r235153

- Include a tiny fix to an upstream bug
(https://llvm.org/bugs/show_bug.cgi?id=23436)
- Use BufferOutputStream instead of FormattedOutputStream in
slang_backend

Change-Id: I9c53b6bbbcccc95513b45d8f0374ced35f7baccd
(cherry picked from commit 21cc01860b95cad7ae60c686e511e8f4ae034e39)
/frameworks/compile/slang/BitWriter_3_2/ValueEnumerator.cpp
c706907a8041faaa882f9bd87f1d1c1669023a62 18-Mar-2015 Stephen Hines <srhines@google.com> Update slang for LLVM rebase to r230699.

Change-Id: I6fa2c59b1445735e2eb95deb4ac503cb9ed369ee
/frameworks/compile/slang/BitWriter_3_2/ValueEnumerator.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/ValueEnumerator.cpp
0da7f6c8201b27938d3b9f048d71fd784cd1df9a 06-Mar-2013 Stephen Hines <srhines@google.com> Updates for LLVM merge to r176139.

Change-Id: I0d0d32893b4638eef298c99ac8c862c9a9bca1a6
/frameworks/compile/slang/BitWriter_3_2/ValueEnumerator.cpp
23c4358f12bd9d0ba7166eceebd683db95a41b3f 10-Jan-2013 Stephen Hines <srhines@google.com> Updates for LLVM merge to r171906 on 20130108.

Change-Id: I4cf3718041d8876d4a23a412b6b4fa4226ec3b50
/frameworks/compile/slang/BitWriter_3_2/ValueEnumerator.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/ValueEnumerator.cpp