Displaying 6 results from an estimated 6 matches for "4j0b5tr8".
2018 Mar 15
2
Commit module to Git after each Pass
...oduce a clear way to separate module IRs as those are being
> printed by -print-after-all
>
> But yes, it should work, and a wrapper that pipes to git fast-import
> seems to be the best way to handle it.
A simple 20-lines perl script does the trick pretty easily:
https://pastebin.com/4J0b5Tr8
(this assumes my local modification to introduce the *** END OF ** IR
DUMP marked at the end of -print-module-scope's IR module dump)
] git init
] RA/bin/opt -O3 some-ir.ll -disable-output -print-after-all
-print-module-scope 2>&1 | filter-LLVM-ir-print.pl | git fast-import
--done -...
2018 Mar 15
0
Commit module to Git after each Pass
...ate module IRs as those are being
>> printed by -print-after-all
>>
>> But yes, it should work, and a wrapper that pipes to git fast-import
>> seems to be the best way to handle it.
> A simple 20-lines perl script does the trick pretty easily:
> https://pastebin.com/4J0b5Tr8
>
> (this assumes my local modification to introduce the *** END OF ** IR
> DUMP marked at the end of -print-module-scope's IR module dump)
>
> ] git init
> ] RA/bin/opt -O3 some-ir.ll -disable-output -print-after-all
> -print-module-scope 2>&1 | filter-LLVM-ir-pri...
2018 Mar 15
2
Commit module to Git after each Pass
...being
> >> printed by -print-after-all
> >>
> >> But yes, it should work, and a wrapper that pipes to git fast-import
> >> seems to be the best way to handle it.
> > A simple 20-lines perl script does the trick pretty easily:
> > https://pastebin.com/4J0b5Tr8
> >
> > (this assumes my local modification to introduce the *** END OF ** IR
> > DUMP marked at the end of -print-module-scope's IR module dump)
> >
> > ] git init
> > ] RA/bin/opt -O3 some-ir.ll -disable-output -print-after-all
> > -print-module-scope...
2018 Mar 15
0
Commit module to Git after each Pass
For this to be really usable in this setup we need additionally to:
- extend -print-module-scope to cover basic block passes
- introduce a clear way to separate module IRs as those are being
printed by -print-after-all
But yes, it should work, and a wrapper that pipes to git fast-import
seems to be the best way to handle it.
regards,
Fedor.
On 03/15/2018 12:31 AM, Daniel Neilson via
2018 Mar 15
0
Commit module to Git after each Pass
...by -print-after-all
> >>
> >> But yes, it should work, and a wrapper that pipes to git
> fast-import
> >> seems to be the best way to handle it.
> > A simple 20-lines perl script does the trick pretty easily:
> > https://pastebin.com/4J0b5Tr8
> >
> > (this assumes my local modification to introduce the *** END OF
> ** IR
> > DUMP marked at the end of -print-module-scope's IR module dump)
> >
> > ] git init
> > ] RA/bin/opt -O3 some-ir.ll -disable-output -print-after-...
2018 Mar 14
2
Commit module to Git after each Pass
The print-module-after-all type of option exists in upstream:
-print-module-scope - When printing IR for print-[before|after]{-all} always print a module IR
commit 7d160f714357f6784ead669ce516e94991c12e5a
Author: Fedor Sergeev <fedor.sergeev at azul.com<mailto:fedor.sergeev at azul.com>>
Date: Fri Dec 1 17:42:46 2017 +0000
IR