History log of /frameworks/compile/slang/BitWriter_3_2/BitcodeWriter.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
77c6e1975c9f75ca136d3c6701b95074a465c7d3 08-Apr-2016 Stephen Hines <srhines@google.com> Fix ConstantDataSequential encoding for half-precision floats.

Bug: http://b/28080406

Although we fixed scalar half-precision constant encoding in our 3.2
BitcodeWriter, we missed the array encoding, so half-precision values
were mistakenly reading/writing a larger double value. Note that this
doesn't change the bitcode encoding for float or double here. Prior LLVM
versions also didn't do a good job of coalescing half-precision values,
so had never needed to encode this value until recently.

(cherry picked from commit 677062a5d170bad26050715d0bf0c333ac69fb5f)

Change-Id: I8feda00581349e35c6ba0bd789404f9883937f65
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
1906a00dce8e32fe3bb8a957e333ebbbee0888e3 29-Jun-2015 Pirama Arumuga Nainar <pirama@google.com> Update Slang for LLVM rebase to r239765

Change-Id: I397b780af624f4a78382e9ec74e58e038aa9d2dc
21cc01860b95cad7ae60c686e511e8f4ae034e39 06-May-2015 Pirama Arumuga Nainar <pirama@google.com> Update slang for rebase to LLVM r235153

- Include a tiny fix to an upstream bug
- Use BufferOutputStream instead of FormattedOutputStream in

Change-Id: I9c53b6bbbcccc95513b45d8f0374ced35f7baccd
c706907a8041faaa882f9bd87f1d1c1669023a62 18-Mar-2015 Stephen Hines <srhines@google.com> Update slang for LLVM rebase to r230699.

Change-Id: I6fa2c59b1445735e2eb95deb4ac503cb9ed369ee
ee4016d1247d3fbe50822de279d3da273d8aef4c 11-Apr-2014 Tim Murray <timmurray@google.com> Update Slang for Clang/LLVM 3.5a.

Change-Id: Icd59efa1197098076555c505c31939866e504a83
eeb251e8db802b836af7461d0f6eb1252c527ab8 11-Feb-2014 Stephen Hines <srhines@google.com> Update slang for LLVM 3.4 rebase.

Remove LinkOnceODRAutoHideLinkage, since it is now just a special case of

Remove CaseRange expansion code from all bitcode writers, since it is now dead.

Fix up HeaderSearch constructor.

Change-Id: I38547486be509b16ea5d8218b43c31ae35b37d3b
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
4e85e8cdbb7d546d45d12ad2f661fbdc9e1597e5 21-Jun-2013 Stephen Hines <srhines@google.com> Merge "Remove unused option from BitWriter_3_2"
70e8843d4a96624adce4ba3de0fcedd8483b0877 21-Jun-2013 Tobias Grosser <grosser@google.com> Remove unused option from BitWriter_3_2

When linking two different BitWriters, this option collides with the
one in current. As it is not used, we just remove it.

Change-Id: I0e1023fae311f487db9c37f67aac4ba54e5aef66
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

Change-Id: Ib6afc5ae405303881605c51c34b6966e4754c29d
0da7f6c8201b27938d3b9f048d71fd784cd1df9a 06-Mar-2013 Stephen Hines <srhines@google.com> Updates for LLVM merge to r176139.

Change-Id: I0d0d32893b4638eef298c99ac8c862c9a9bca1a6
23c4358f12bd9d0ba7166eceebd683db95a41b3f 10-Jan-2013 Stephen Hines <srhines@google.com> Updates for LLVM merge to r171906 on 20130108.

Change-Id: I4cf3718041d8876d4a23a412b6b4fa4226ec3b50
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