search for: d44132

Does https://reviews.llvm.org/D44132 <https://reviews.llvm.org/D44132> help at all? > On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The most likely answer is that the printer used by print-after-all is slow. I know there were some changes made around passing in som...

...n module) In any case, it is, to me, much more usable (and extensible) than -print-after-all. But requires git to be in PATH (I'm curious if that works on Windows). On Thu, Mar 15, 2018 at 1:35 PM, Daniel Sanders <daniel_l_sanders at apple.com> wrote: > Does https://reviews.llvm.org/D44132 help at all? > > > On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > The most likely answer is that the printer used by print-after-all is > slow. I know there were some changes made around passing in some form of > state...

The most likely answer is that the printer used by print-after-all is slow.  I know there were some changes made around passing in some form of state cache (metadata related?) and that running printers without doing so work, but are dog slow.  I suspect the print-after-all support was never updated.  Look at what we do for the normal IR emission "-S" and see if print-after-all is

Huh. Great! 😁 I don't believe my poor excuse from earlier (else we should map all pipes into files!), but I'm curious why we spend less time in system mode when going through file than pipe. Maybe /dev/null is not as efficient as we might think? I can't believe I'm saying that... On Thu, Mar 15, 2018, 08:25 Fedor Sergeev <fedor.sergeev at azul.com> wrote: > Well, git by

...t; -print-after-all. But requires git to be in PATH (I'm curious if that > works on Windows). > > On Thu, Mar 15, 2018 at 1:35 PM, Daniel Sanders > <daniel_l_sanders at apple.com <mailto:daniel_l_sanders at apple.com>> wrote: > > Does https://reviews.llvm.org/D44132 > <https://reviews.llvm.org/D44132> help at all? > > >> On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev >> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> The most likely answer is that the printer...

...e) than > -print-after-all. But requires git to be in PATH (I'm curious if that works > on Windows). > >> > >> On Thu, Mar 15, 2018 at 1:35 PM, Daniel Sanders < > daniel_l_sanders at apple.com> wrote: > >> > >> Does https://reviews.llvm.org/D44132 help at all? > >> > >> > >>> On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >>> > >>> The most likely answer is that the printer used by print-after-all > is slow. I know there...

...ch more usable (and extensible) than -print-after-all. But requires git to be in PATH (I'm curious if that works on Windows). >> >> On Thu, Mar 15, 2018 at 1:35 PM, Daniel Sanders <daniel_l_sanders at apple.com> wrote: >> >>     Does https://reviews.llvm.org/D44132 help at all? >> >> >>>     On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>>     The most likely answer is that the printer used by print-after-all is slow.  I know there were some changes made around...

...in PATH (I'm curious if that >> > works on Windows). >> > >> >> > >> On Thu, Mar 15, 2018 at 1:35 PM, Daniel Sanders >> > <daniel_l_sanders at apple.com> wrote: >> > >> >> > >> Does https://reviews.llvm.org/D44132 help at all? >> > >> >> > >> >> > >>> On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev >> > <llvm-dev at lists.llvm.org> wrote: >> > >>> >> > >>> The most likely answer is that the printer...

...than > -print-after-all. But requires git to be in PATH (I'm curious if that > works on Windows). > >> > >> On Thu, Mar 15, 2018 at 1:35 PM, Daniel Sanders > <daniel_l_sanders at apple.com> wrote: > >> > >>     Does https://reviews.llvm.org/D44132 help at all? > >> > >> > >>>     On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >>> > >>>     The most likely answer is that the printer used by > print-after-all is slow.  I know there...

...git to be in PATH (I'm curious if that > works on Windows). > >> > >> On Thu, Mar 15, 2018 at 1:35 PM, Daniel Sanders > <daniel_l_sanders at apple.com<mailto:daniel_l_sanders at apple.com>> wrote: > >> > >> Does https://reviews.llvm.org/D44132 help at all? > >> > >> > >>> On 15 Mar 2018, at 09:16, Philip Reames via llvm-dev > <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: > >>> > >>> The most likely answer is that the printer used by >...