Displaying 4 results from an estimated 4 matches for "postipo".
2013 Jul 29
5
[LLVMdev] IR Passes and TargetTransformInfo: Straw Man
...e basically very stable. As far as I can tell from the result,
> the proposed pass-ordering is basically toward good change.
>
> Interesting enough, if I combine the populatePreIPOPassMgr() as the preIPO phase
> (see the patch) with original populateLTOPassManager() for both IPO and postIPO,
> I see significant improve to "Benchmarks/Trimaran/netbench-crc/netbench-crc"
> (about 94%, 0.5665s(was) vs 0.0295s), as of I write this mail, I have not yet got chance
> to figure out why this combination improves this benchmark this much.
>
> In teams of compile-tim...
2013 Jul 29
0
[LLVMdev] IR Passes and TargetTransformInfo: Straw Man
...; > from the result,
> > the proposed pass-ordering is basically toward good change.
> >
> > Interesting enough, if I combine the populatePreIPOPassMgr() as
> > the preIPO phase
> > (see the patch) with original populateLTOPassManager() for both IPO
> > and postIPO,
> > I see significant improve to
> > "Benchmarks/Trimaran/netbench-crc/netbench-crc"
> > (about 94%, 0.5665s(was) vs 0.0295s), as of I write this mail, I
> > have not yet got chance
> > to figure out why this combination improves this benchmark this
> >...
2013 Jul 28
0
[LLVMdev] IR Passes and TargetTransformInfo: Straw Man
...ult twice, they are basically very stable. As far as I can tell from
the result,
the proposed pass-ordering is basically toward good change.
Interesting enough, if I combine the populatePreIPOPassMgr() as the
preIPO phase
(see the patch) with original populateLTOPassManager() for both IPO and
postIPO,
I see significant improve to
"Benchmarks/Trimaran/netbench-crc/netbench-crc"
(about 94%, 0.5665s(was) vs 0.0295s), as of I write this mail, I have
not yet got chance
to figure out why this combination improves this benchmark this much.
In teams of compile-time, the result reports my...
2013 Jul 18
3
[LLVMdev] IR Passes and TargetTransformInfo: Straw Man
Andy and I briefly discussed this the other day, we have not yet got
chance to list a detailed pass order
for the pre- and post- IPO scalar optimizations.
This is wish-list in our mind:
pre-IPO: based on the ordering he propose, get rid of the inlining (or
just inline tiny func), get rid of
all loop xforms...
post-IPO: get rid of inlining, or maybe we still need it, only