search for: writemoduleconstants

...g out, so would like some pointers if possible. The proximate cause of the issue in our local version of llvm is that a Value is being written out, and the dump() of that value is actually not a value at all, but what looks like a reference to a function. So what happens is that BitcodeWriter.cpp:WriteModuleConstants() is barfing, because this particular Value is not any of the variants that its made to handle. It looks like the specific value in question is part of the debug metadata generated by our local version (which is somewhere between v2.7 and the llvm-tip, plus our local changes) Interestingly enough...

...OCK abbrev id's. > + // FUNCTION_BLOCK_REL abbrev id's. Should this comment have been changed? > FUNCTION_INST_LOAD_ABBREV = bitc::FIRST_APPLICATION_ABBREV, > FUNCTION_INST_BINOP_ABBREV, > FUNCTION_INST_BINOP_FLAGS_ABBREV, ... > @@ -1025,12 +1037,15 @@ static void WriteModuleConstants(const ValueEnumerator &VE, > /// > /// This function adds V's value ID to Vals. If the value ID is higher than the > /// instruction ID, then it is a forward reference, and it also includes the > -/// type ID. > +/// type ID. The value ID that is writtne is encoded as re...

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