search for: bitstreamwrit

...9;m afraid this question is extremely basic, but i've assumed that dumping a .bc file from a module was a trivial operation, but now, first time i have to actually do it from code, for the life of me i can't find one missing step in the process: static void WriteModule ( const Module * M, BitstreamWriter & Stream ) http://llvm.org/docs/doxygen/html/BitcodeWriter_8cpp.html#a828cec7a8fed9d232556420efef7ae89 to write that module, first i need a BistreamWriter BitstreamWriter::BitstreamWriter (SmallVectorImpl< char > &O) http://llvm.org/docs/doxygen/html/classllvm_1_1BitstreamWriter....

...yes many places are drifting a lot in LLVM...). > > Not to say that it can't be done, just that it requires a lot of care. I don't think we should throw *all* the state in. But some of the state is passed everywhere. At least (off the top of my head): - ValueEnumerator& - BitstreamWriter&

...irs for varargs params. > if (FTy->isVarArg()) { ... > @@ -1514,8 +1553,8 @@ static void WriteFunction(const Function &F, ValueEnumerator &VE, > // Emit blockinfo, which defines the standard abbreviations etc. > static void WriteBlockInfo(const ValueEnumerator &VE, BitstreamWriter &Stream) { > // We only want to emit block info records for blocks that have multiple > - // instances: CONSTANTS_BLOCK, FUNCTION_BLOCK and VALUE_SYMTAB_BLOCK. Other > - // blocks can defined their abbrevs inline. > + // instances: CONSTANTS_BLOCK, FUNCTION_BLOCK_REL and VA...

Hi all, I've been looking into how to make llvm bitcode files smaller. There is one simple change that appears to shrink linked bitcode files by about 15%. See this spreadsheet for some rough data: https://docs.google.com/spreadsheet/ccc?key=0AjRrJHQc4_bddEtJdjdIek5fMDdIdFFIZldZXzdWa0E The change is in how operand ids are encoded in bitcode files. Rather than use an "absolute

I am currently making some BitcodeWriter changes that involve some refactoring, and am thinking for the Nth time that it would be much nicer to have a class instead of passing around a long list of parameters. I am thinking of biting the bullet and doing that - any objections? I assume the reason why there is no existing class wrapping the bitcode writing process is just legacy code and nothing

> It is simpler. There is not any Mach-O envelope. The platform linker > can directly read Mach-O files as well as llvm bit-code file (using > llvm bit-code file reader). > > > Not sure if/where the exact form of the Mach-O file that carries bit > > code is documented. Thanks for that. Yes, I see what you mean (no Mach-O envelope), yet there seems to be something

> Aaah. Wasn't quite sure what you were doing here. I'm not positive > what llvm can emit via the writers (there's support for all parts of > the file format), but it could be extended to write one out. I'm just > not quite sure why :) > > -eric Well, ultimately I'm curious about what it would take to port a JVM based language (http://openquark.org) to

Hi all, We're hitting some walls here when generating the correct structure layout for specific C++ ABI requirements, and I was wondering how much StructLayout could help. For instance, the ABI has some complicated rules on the size of derived classes (http://www.codesourcery.com/public/cxx-abi/abi.html#class-types) and LLVM struct type cannot reflect that in full. Example: // CHECK:

On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>

.../local/llvm-2.8/include/llvm/Bitcode -- Installing: /usr/local/llvm-2.8/include/llvm/Bitcode/Archive.h -- Installing: /usr/local/llvm-2.8/include/llvm/Bitcode/BitCodes.h -- Installing: /usr/local/llvm-2.8/include/llvm/Bitcode/BitstreamReader.h -- Installing: /usr/local/llvm-2.8/include/llvm/Bitcode/BitstreamWriter.h -- Installing: /usr/local/llvm-2.8/include/llvm/Bitcode/LLVMBitCodes.h -- Installing: /usr/local/llvm-2.8/include/llvm/Bitcode/ReaderWriter.h -- Installing: /usr/local/llvm-2.8/include/llvm/CMakeLists.txt -- Installing: /usr/local/llvm-2.8/include/llvm/CallGraphSCCPass.h -- Installing: /usr/loc...

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel