search for: pushvalue

...gher 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 relative to the InstID. writtne -> written is encoded as relative to -> is encoded relative to > static bool PushValueAndType(const Value *V, unsigned InstID, > SmallVector<unsigned, 64> &Vals, > ValueEnumerator &VE) { > unsigned ValID = VE.getValueID(V); > - Vals.push_back(ValID); > + if (EnableOldStyleFunctions) > +...

...2 at 8:32 AM, Rafael Espíndola <rafael.espindola at gmail.com > wrote: > > +static void EmitSignedInt64(SmallVectorImpl<uint64_t> &Vals, uint64_t V) { > > Please start function names with a lower case letter. > > Done -- changed this function and most of the "pushValue" functions. I left PushValueAndType alone since that is an existing function and it seemed like that would introduce other unrelated changes. > +EnableOldStyleFunctions("enable-old-style-functions", > > Maybe something like use-abs-operands is a better name now that this...

> Thanks for taking a look! I wasn't sure of better way to toggle this > behavior at the module level vs the function level. The options I toyed > with were: > > (a) bump MODULE_CODE_VERSION from 0 to 1 > (b) add a new optional module code to identify the change > (c) stick with the approach in the first patch, which used a new function > block ID value, then

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

On Sun, Sep 30, 2012 at 9:09 AM, Chris Lattner <clattner at apple.com> wrote: > > On Sep 25, 2012, at 5:08 PM, Jan Voung <jvoung at chromium.org> wrote: > > 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

On Nov 14, 2012, at 12:47 PM, Chris Lattner <clattner at apple.com> wrote: > > On Nov 14, 2012, at 12:28 PM, Michael Ilseman <milseman at apple.com> wrote: > >> I think I missed what problem we're trying to solve here. >> >> I'm looking at implementing the bitcode now. I have code to successfully read and write out the LLVM IR textual formal

...--git a/lib/Bitcode/Writer/BitcodeWriter.cpp b/lib/Bitcode/Writer/BitcodeWriter.cpp index 718cd12..0093c0f 100644 --- a/lib/Bitcode/Writer/BitcodeWriter.cpp +++ b/lib/Bitcode/Writer/BitcodeWriter.cpp @@ -1441,9 +1441,11 @@ static void WriteInstruction(const Instruction &I, unsigned InstID, pushValue(I.getOperand(2), InstID, Vals, VE); // newval. Vals.push_back(cast<AtomicCmpXchgInst>(I).isVolatile()); Vals.push_back(GetEncodedOrdering( - cast<AtomicCmpXchgInst>(I).getOrdering())); + cast<AtomicCmpXchgInst>(I).getSucces...