search for: bitwriter_3_2

Displaying 6 results from an estimated 6 matches for "bitwriter_3_2".

LLVM bc converter from LLVM 3.9 to LLVM 3.1
2016 Aug 03
2
LLVM bc converter from LLVM 3.9 to LLVM 3.1
...arately-maintained LLVM 3.2 BticodeWriter to generate the > downgraded form. We also have 2 other BitcodeWriters based on roughly LLVM > 2.9 (but not exactly 2.9, so I would steer you away from those). > https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/ > is a link to the actual primary writer we use. > > >> >>> >>> Does this took work on LLVM 3.9svn? >>> >> > It currently only works up to LLVM r256229. We will most likely be > updating it to closer to TOT LLVM in the next few months, but it i...
LLVM bc converter from LLVM 3.9 to LLVM 3.1
2016 Aug 03
3
LLVM bc converter from LLVM 3.9 to LLVM 3.1
...s, we use a separately-maintained LLVM 3.2 BticodeWriter to generate the downgraded form. We also have 2 other BitcodeWriters based on roughly LLVM 2.9 (but not exactly 2.9, so I would steer you away from those). https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/ <https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/> is a link to the actual primary writer we use. > > > > Does this took work on LLVM 3.9svn? > > It currently only works up to LLVM r256229. We will most likely be upd...
LLVM bc converter from LLVM 3.9 to LLVM 3.1
2016 Aug 03
2
LLVM bc converter from LLVM 3.9 to LLVM 3.1
...erate >>>>> the downgraded form. We also have 2 other BitcodeWriters based on roughly >>>>> LLVM 2.9 (but not exactly 2.9, so I would steer you away from those). >>>>> https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/ >>>>> is a link to the actual primary writer we use. >>>>> >>>>> >>>>>> >>>>>>> >>>>>>> Does this took work on LLVM 3.9svn? >>>>>>> >>>>>> >>>&gt...
[LLVMdev] How to make sure the compatibility of LLVM IR
2014 Jun 01
2
[LLVMdev] How to make sure the compatibility of LLVM IR
Hello all, We have our own C++ language extension (based on Clang 3.2) and its special backend (implemented in LLVM 3.2). Now we want to upgrade Clang to version 3.3 or 3.4, and the backend (llc) is still remained in LLVM 3.2. (aka. compile our own C++ language extension to LLVM 3.3/3.4 IR, and use LLVM 3.2 llc to generate its special backend assembly). I already know that LLVM assembly has
LLVM bc converter from LLVM 3.9 to LLVM 3.1
2016 Aug 03
2
LLVM bc converter from LLVM 3.9 to LLVM 3.1
...s, we use a separately-maintained LLVM 3.2 BticodeWriter to generate the downgraded form. We also have 2 other BitcodeWriters based on roughly LLVM 2.9 (but not exactly 2.9, so I would steer you away from those). https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/ <https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/> is a link to the actual primary writer we use. >> >> >> >> Does this took work on LLVM 3.9svn? >> >> It currently only works up to LLVM r256229. We...
LLVM bc converter from LLVM 3.9 to LLVM 3.1
2016 Aug 03
2
LLVM bc converter from LLVM 3.9 to LLVM 3.1
> > I also have a look at the code, looks like it directly parse the bitcode > and build in memory representation in a different LLVM version than the > bitcode. Is this correct? According to your description, I guess the BitCodeWriter should be the one > to do the bitcode version downgrade, right? I think so. I don't know much about it and don't want to give you