search for: d63034

...is working quite well otherwise. > > Our current list of issues: > 1) Libsqlite still has a mysterious failure that we haven't been able to reduce well. > 2) https://bugs.llvm.org/show_bug.cgi?id=42124 shows that inlining costs are a bit different under NPM. https://reviews.llvm.org/D63034 is one proposed patch for addressing this. > 3) libpdfium exposed a non-determinism issue with NPM where having the linux-libc-dev system package installed changes execution. We are still looking at why this happens. > 4) Sanitizer coverage information isn't supported by the NPM yet (http...

On Thu, 27 Jun 2019 at 17:46, Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > For our downstream usage, we've switched entirely to the new pass manager. We made the switch a couple of months ago. All of our testing is being done with the NPM, and we're about to start deleting (downstream) code which was only needed by the legacy pass manager. > > I

...t; > > Our current list of issues: > > > 1) Libsqlite still has a mysterious failure that we haven't been able to reduce > well. > > > 2) https://bugs.llvm.org/show_bug.cgi?id=42124 shows that inlining costs > are a bit different under NPM. https://reviews.llvm.org/D63034 is one proposed > patch for addressing this. > > > 3) libpdfium exposed a non-determinism issue with NPM where having the > linux-libc-dev system package installed changes execution. We are still looking > at why this happens. > > > 4) Sanitizer coverage information isn...

...ues: >> > > > 1) Libsqlite still has a mysterious failure that we haven't been able to reduce >> > well. >> > > > 2) https://bugs.llvm.org/show_bug.cgi?id=42124 shows that inlining costs >> > are a bit different under NPM. https://reviews.llvm.org/D63034 is one proposed >> > patch for addressing this. >> > > > 3) libpdfium exposed a non-determinism issue with NPM where having the >> > linux-libc-dev system package installed changes execution. We are still looking >> > at why this happens. >> > >...

...ll has a mysterious failure that we haven't been >> able to reduce >> >> > well. >> >> > > > 2) https://bugs.llvm.org/show_bug.cgi?id=42124 shows that >> inlining costs >> >> > are a bit different under NPM. https://reviews.llvm.org/D63034 is >> one proposed >> >> > patch for addressing this. >> >> > > > 3) libpdfium exposed a non-determinism issue with NPM where >> having the >> >> > linux-libc-dev system package installed changes execution. We are >> still looking...

...n't been able to reduce >> >> > well. >> >> > > > 2) https://bugs.llvm.org/show_bug.cgi?id=42124 shows >> that inlining costs >> >> > are a bit different under NPM. >> https://reviews.llvm.org/D63034 is one proposed >> >> > patch for addressing this. >> >> > > > 3) libpdfium exposed a non-determinism issue with >> NPM where having the >> >> > linux-libc-dev system package installed changes >>...

...>> > well. >>> >> > > > 2) https://bugs.llvm.org/show_bug.cgi?id=42124 >>> shows that inlining costs >>> >> > are a bit different under NPM. >>> https://reviews.llvm.org/D63034 is one proposed >>> >> > patch for addressing this. >>> >> > > > 3) libpdfium exposed a non-determinism issue >>> with NPM where having the >>> >> > linux-libc-dev system package ins...