Displaying 3 results from an estimated 3 matches for "6965f1e1".
2018 Mar 15
0
Commit module to Git after each Pass
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
2018 Mar 15
2
Commit module to Git after each Pass
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
2018 Mar 15
3
Commit module to Git after each Pass
..._________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180315/6965f1e1/attachment.html>