search for: inst_phi

Yes, I had about 133K hits for INST_PHI with a negative value, out of 136K hits of any "INST_.*" with a negative valued operand. Overall there were 474K INST_PHI and 12 million "INST_.*" in my tests. - Jan On Wed, Oct 10, 2012 at 11:23 AM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > This l...

On 10 October 2012 15:15, Jan Voung <jvoung at chromium.org> wrote: > Yes, I had about 133K hits for INST_PHI with a negative value, out of 136K > hits of any "INST_.*" with a negative valued operand. > > Overall there were 474K INST_PHI and 12 million "INST_.*" in my tests. Cool! Thanks again for working on this! > - Jan Cheers, Rafael

On Sat, Oct 6, 2012 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

This looks good to me. Just one question, you found that forward references are only common with phi operands, so it is not profitable to use a signed representation for other operands, right? Cheers, Rafael

...ew Rafael! Chris, did you want to take a look at the patch too? Thanks, - Jan On Wed, Oct 10, 2012 at 12:39 PM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > On 10 October 2012 15:15, Jan Voung <jvoung at chromium.org> wrote: > > Yes, I had about 133K hits for INST_PHI with a negative value, out of > 136K > > hits of any "INST_.*" with a negative valued operand. > > > > Overall there were 474K INST_PHI and 12 million "INST_.*" in my tests. > > Cool! > > Thanks again for working on this! > > > - Jan &gt...

...OCA 8444 692924 INST_CALL 5714 217132 100.00 INST_CAST 4370 54722 100.00 INST_RET 4370 96188 DECLAREBLOCKS 3791 263822 INST_INBOUNDS_GEP 2209 64912 INST_BR 1805 173588 INST_INVOKE 1269 88794 INST_GEP 476 30464 INST_CMP2 445 1780 100.00 INST_UNREACHABLE 161 7378 100.00 INST_BINOP 21 1488 INST_PHI 4 160 INST_EXTRACTVAL 1 94 INST_SWITCH The above tells you there are 4379 functions in the bitcode file. Globally, there are 11024 stores, 10930 loads, 10519 allocas, etc. Obtaining details on a per-function basis may require hacking the bitcode-analyzer a bit (llvm/tools/llvm-bcanalyzer/llvm-b...

...format (run llvm-bcanalyzer -dump to see the difference). Caveats: - Forward references will create negative-valued ids (which end up being written out as large 32-bit integers, as far as I could tell). The common case for this is PHI nodes, but in larger tests fewer bits *overall* are used for INST_PHI. - Doesn't help with constant operands. Their ids will now constantly change... - To retain backward compatibility with old bitcode files, I ended up using up a new bitc value "bitc::FUNCTION_BLOCK_REL_ID" vs the existing "bitc::FUNCTION_BLOCK_ID". Are there known proble...