search for: nonload

...st > environments, a core dump does not need to have debug info or symbol names > in it, but can be still be read in full detail in conjunction with the > original binary. Yes -- there are many alternatives: 1) emit the name key mapping as a side data at compile time, or 2) emit them into nonloadable sections of the object file. Compared with the above, LLVM's existing design does have its own advantage -- making it easier for tool to access 'debug' info for counters. LLVM's coverage testing, on the other hand, take a hybrid approach: It emits the coverage map as rodata, b...

...or symbol >> > names >> > in it, but can be still be read in full detail in conjunction with the >> > original binary. >> >> Yes -- there are many alternatives: >> 1) emit the name key mapping as a side data at compile time, or >> 2) emit them into nonloadable sections of the object file. >> >> Compared with the above, LLVM's existing design does have its own >> advantage -- making it easier for tool to access 'debug' info for >> counters. >> >> LLVM's coverage testing, on the other hand, take a hyb...

...be read in full detail in conjunction with >> >> > the >> >> > original binary. >> >> >> >> Yes -- there are many alternatives: >> >> 1) emit the name key mapping as a side data at compile time, or >> >> 2) emit them into nonloadable sections of the object file. >> >> >> >> Compared with the above, LLVM's existing design does have its own >> >> advantage -- making it easier for tool to access 'debug' info for >> >> counters. >> >> >> >> LLVM...

...gt;>> >> > the >>>> >> > original binary. >>>> >> >>>> >> Yes -- there are many alternatives: >>>> >> 1) emit the name key mapping as a side data at compile time, or >>>> >> 2) emit them into nonloadable sections of the object file. >>>> >> >>>> >> Compared with the above, LLVM's existing design does have its own >>>> >> advantage -- making it easier for tool to access 'debug' info for >>>> >> counters. >>...

Hi, I want to improve the way CGP sinks the incoming values of a PHI node towards memory accesses. Improving it means a lot to some of our key benchmarks, and I believe can benefit many general cases as well. CGP's OptimizeMemoryInst function handles PHI nodes by running AddressingModeMatcher on all incoming values to see whether they reach consensus on the addressing mode. It does a

On Fri, Sep 4, 2015 at 11:03 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Fri, Sep 4, 2015 at 10:11 PM, Xinliang David Li <davidxl at google.com> > wrote: >> >> On Fri, Sep 4, 2015 at 9:11 PM, Sean Silva <chisophugis at gmail.com> wrote: >> > >> > >> > On Fri, Sep 4, 2015 at 5:42 PM, Xinliang David Li <davidxl at