search for: parsemetadataattach

Displaying 5 results from an estimated 5 matches for "parsemetadataattach".

2009 Oct 31
3
[LLVMdev] Something wrong with my libpthread.so
...signal + 53 4 libc.so.6 0x0000003df2834b20 abort + 384 5 libc.so.6 0x0000003df282c2fa __assert_fail + 234 6 lli 0x000000000085ece9 llvm::SmallVectorImpl<llvm::Instruction*>::operator[](unsigned int) + 77 7 lli 0x0000000000850ce0 llvm::BitcodeReader::ParseMetadataAttachment() + 448 8 lli 0x0000000000851043 llvm::BitcodeReader::ParseFunctionBody(llvm::Function*) + 677 9 lli 0x0000000000854b29 llvm::BitcodeReader::materializeFunction(llvm::Function*, std::string*) + 323 10 lli 0x0000000000c6a073 llvm::JIT::getPointerToFunctio...
2009 Nov 01
0
[LLVMdev] Something wrong with my libpthread.so
...       0x0000003df2834b20 abort + 384 > 5   libc.so.6       0x0000003df282c2fa __assert_fail + 234 > 6   lli             0x000000000085ece9 > llvm::SmallVectorImpl<llvm::Instruction*>::operator[](unsigned int) + 77 > 7   lli             0x0000000000850ce0 > llvm::BitcodeReader::ParseMetadataAttachment() + 448 > 8   lli             0x0000000000851043 Looks like a bug in the following piece of code, from BitcodeReader::ParseMetadataAttachment(): 1601 case bitc::METADATA_ATTACHMENT: { 1602 unsigned RecordLength = Record.size(); 1603 if (Record.empty() || (RecordLength...
2009 Nov 01
1
[LLVMdev] Something wrong with my libpthread.so
...34b20 abort + 384 >> 5 libc.so.6 0x0000003df282c2fa __assert_fail + 234 >> 6 lli 0x000000000085ece9 >> llvm::SmallVectorImpl<llvm::Instruction*>::operator[](unsigned int) + 77 >> 7 lli 0x0000000000850ce0 >> llvm::BitcodeReader::ParseMetadataAttachment() + 448 >> 8 lli 0x0000000000851043 > > Looks like a bug in the following piece of code, from > BitcodeReader::ParseMetadataAttachment(): > > 1601 case bitc::METADATA_ATTACHMENT: { > 1602 unsigned RecordLength = Record.size(); > 1603...
2012 Sep 26
0
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
...he use of relative ids was on a per module basis then this wouldn't be needed. > + > if (RememberAndSkipFunctionBody()) > return true; > // For streaming bitcode, suspend parsing when we reach the function > @@ -1901,8 +1909,15 @@ bool BitcodeReader::ParseMetadataAttachment() { > > /// ParseFunctionBody - Lazily parse the specified function body block. > bool BitcodeReader::ParseFunctionBody(Function *F) { > - if (Stream.EnterSubBlock(bitc::FUNCTION_BLOCK_ID)) > - return Error("Malformed block record"); > + if (FuncUseRelativeIDs...
2012 Sep 26
9
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
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