Displaying 3 results from an estimated 3 matches for "3a663688".
2018 Mar 14
0
Commit module to Git after each Pass
This is interesting, and might be useful. I don't know that this is
broadly useful enough for upstream inclusion, but if you could post this
to github somewhere, I might play with it.
There might also be room to factor out common functionality. We've also
run into the need to print whole-module instead of containing construct
(i.e. this loop). If we added upstream support for
2018 Mar 14
2
Commit module to Git after each Pass
...LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto: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/20180314/3a663688/attachment-0001.html>
2018 Mar 06
6
Commit module to Git after each Pass
Hello,
I had a stupid idea recently that turned out not so stupid after all. I
wanted to be able to "see" an entire pass pipeline in action to find
unnecessary transformations and/or missed opportunities and generally
improve the debug-ability of LLVM.
So as the title suggest, I implemented an equivalent of "-print-after-all"
but instead of printing into stdout I dump into a