search for: bitstreamread

Hi all, BitstreamReader is the only in-tree client of the DataStreamer and MemoryObject interfaces. In practice when using user-facing LLVM tools, the bitcode will normally either be in memory or in a file, so the best way to access it is through memory, either directly or memory mapped. As part of some refactorings I...

Hello, I'm compiling LLVM with MSVC at the moment, I've got the following warning: BitstreamReader.h(327) : warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) in line uint64_t Piece = Read(NumBits); if ((Piece & (1U << (NumBits-1))) == 0) Is this warning relevant? Is also Read64() instead of Re...

...e this thread open until end of Monday to receive any other opinions, then proceed to remove it. Peter [0] http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20161024/400754.html On Fri, Oct 28, 2016 at 10:08 AM, Peter Collingbourne <peter at pcc.me.uk> wrote: > Hi all, > > BitstreamReader is the only in-tree client of the DataStreamer and > MemoryObject interfaces. In practice when using user-facing LLVM tools, the > bitcode will normally either be in memory or in a file, so the best way to > access it is through memory, either directly or memory mapped. > > As part...

...} int main(int argc, char**argv) { mystruct str = {45.0, 2.0, 0.0, 3}; printf("result = %f\n", whatever(&str)); return 0; } Did I miss something fundamental here? Also I've noticed that the BitcodeReader appears to be an internal module, but the BitstreamReader is public. Should I be using the BitstreamReader? If so how. Thank you! -danny

...t; opinions, then proceed to remove it. > > Peter > > [0] > http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20161024/400754.html > > On Fri, Oct 28, 2016 at 10:08 AM, Peter Collingbourne <peter at pcc.me.uk> > wrote: >> >> Hi all, >> >> BitstreamReader is the only in-tree client of the DataStreamer and >> MemoryObject interfaces. In practice when using user-facing LLVM tools, the >> bitcode will normally either be in memory or in a file, so the best way to >> access it is through memory, either directly or memory mapped. >&...

Hi Danny, On 2007-12-26, at 15:39, Danny wrote: > I've noticed that the BitcodeReader appears to be an internal > module, but the BitstreamReader is public. Should I be using the > BitstreamReader? If so how. The generic BitstreamReader class is public because it's used in other projects, including clang, to serialize data structures other than LLVM IR. The coding of the LLVM IR within the bitstream are private to the reade...

Hi all, This is about https://reviews.llvm.org/D26100 That change moves the block info block state from BitstreamReader to BitstreamCursor in order to accommodate multiple block info blocks (the idea is that the cursor would store the block info block state for whichever block info block is active for that cursor). Duncan objected to it on the grounds that we should aim for a design that would continue to allow a...

> On Oct 28, 2016, at 6:00 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > Hi all, > > This is about https://reviews.llvm.org/D26100 <https://reviews.llvm.org/D26100> > > That change moves the block info block state from BitstreamReader to BitstreamCursor in order to accommodate multiple block info blocks (the idea is that the cursor would store the block info block state for whichever block info block is active for that cursor). > > Duncan objected to it on the grounds that we should aim for a design that would continue...

...at into the code itself so it's all contained in one. Thanks, danny On Dec 26, 2007, at 3:33 PM, Gordon Henriksen wrote: > Hi Danny, > > On 2007-12-26, at 15:39, Danny wrote: > >> I've noticed that the BitcodeReader appears to be an internal >> module, but the BitstreamReader is public. Should I be using the >> BitstreamReader? If so how. > > The generic BitstreamReader class is public because it's used in > other projects, including clang, to serialize data structures other > than LLVM IR. The coding of the LLVM IR within the bitstream are...

....amini at apple.com> wrote: > >> >> On Oct 28, 2016, at 6:00 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >> >> Hi all, >> >> This is about https://reviews.llvm.org/D26100 >> >> That change moves the block info block state from BitstreamReader to BitstreamCursor in order to accommodate multiple block info blocks (the idea is that the cursor would store the block info block state for whichever block info block is active for that cursor). >> >> Duncan objected to it on the grounds that we should aim for a design that would c...

...default /usr/local/ "../configure" '--enable-static' '--enable-targets=host-only' '--enable-doxygen' '--with-gnu-ld' make sudo make install But still getting find /usr/local/include/llvm -name 'Bit*eader*' /usr/local/include/llvm/Bitcode/BitstreamReader.h and grep -rni BitcodeReader /usr/local/include/llvm remains desperately silent. Obviously, I made a mistake which I cannot find yet. Any help please? Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6...

...... If you want to try > out the patch, you can toggle between the new and old encoding by using the flag > "-enable-old-style-functions" vs no flags, with llvm-as. I don't know anything much about the bitcode representation, but anyway: > diff --git a/include/llvm/Bitcode/BitstreamReader.h b/include/llvm/Bitcode/BitstreamReader.h > index 3daef78..840f57e 100644 > --- a/include/llvm/Bitcode/BitstreamReader.h > +++ b/include/llvm/Bitcode/BitstreamReader.h > @@ -409,7 +409,7 @@ public: > } > > /// EnterSubBlock - Having read the ENTER_SUBBLOCK abbrevid, en...

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

...n based dissertation with llvm. I am having problems building llvm on OpenBSD-current. I hope to make a port of llvm for OpenBSD once I have figured out how to build it. Observe: llvm[3]: Compiling Deserialize.cpp for Release build In file included from /home/edd/llvm/llvm-2.3/include/llvm/Bitcode/BitstreamRead er.h:18, from /home/edd/llvm/llvm-2.3/include/llvm/Bitcode/Deserialize.h :18, from Deserialize.cpp:14: /home/edd/llvm/llvm-2.3/include/llvm/Bitcode/BitCodes.h:158: warning: `class llvm::BitCodeAbbrev' only defines a private destructor and has no friends llvm...

Hello Willy, Here is the dump from one of my bitcode files: 0000000 42 43 c0 de 21 0c 00 00 25 05 00 00 0b 82 20 00 As expected, 0x42 (= B), 0x43 (= C), xc0 and 0xde are in correct order. In your case, the first byte is read as 37 (= 0x25). I wonder why? When you check the bytes yourself, you get expected results. When the same bytes are read from Stream object, you get a different result (maybe

...talling: /usr/local/llvm-2.8/include/llvm/BasicBlock.h -- Installing: /usr/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: /...

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

...p for Release+Asserts build llvm[3]: Compiling BitcodeWriterPass.cpp for Release+Asserts build llvm[2]: Compiling AliasSetTracker.cpp for Release+Asserts build llvm[3]: Compiling ValueEnumerator.cpp for Release+Asserts build llvm[2]: Compiling Parser.cpp for Release+Asserts build llvm[3]: Compiling BitstreamReader.cpp for Release+Asserts build llvm[2]: Compiling Analysis.cpp for Release+Asserts build llvm[2]: Building Release+Asserts Archive Library libLLVMAsmParser.a llvm[3]: Building Release+Asserts Archive Library libLLVMBitWriter.a make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/Asm...