search for: 340.48

Problem ------- Instrumentation for PGO and frontend-based coverage places a large amount of data in object files, even though the majority of this data is not needed at run-time. All the data is needlessly duplicated while generating archives, and again while linking. PGO name data is written out into raw profiles by instrumented programs, slowing down the training and code coverage workflows.

On Fri, Jun 30, 2017 at 5:54 PM, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Problem > ------- > > Instrumentation for PGO and frontend-based coverage places a large amount > of > data in object files, even though the majority of this data is not needed > at > run-time. All the data is needlessly duplicated while generating archives, > and > again while

On Fri, Jun 30, 2017 at 10:04 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Fri, Jun 30, 2017 at 5:54 PM, via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > >> Problem >> ------- >> >> Instrumentation for PGO and frontend-based coverage places a large amount >> of >> data in object files, even though the majority of this

On Fri, Jun 30, 2017 at 5:54 PM, <vsk at apple.com> wrote: > Problem > ------- > > Instrumentation for PGO and frontend-based coverage places a large amount > of > data in object files, even though the majority of this data is not needed > at > run-time. All the data is needlessly duplicated while generating archives, > and > again while linking. PGO name data

On Fri, Jun 30, 2017 at 10:25 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Fri, Jun 30, 2017 at 10:04 PM, Sean Silva <chisophugis at gmail.com> > wrote: > >> >> >> On Fri, Jun 30, 2017 at 5:54 PM, via llvm-dev <llvm-dev at lists.llvm.org> >> wrote: >> >>> Problem >>> ------- >>> >>>