https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
--- Comment #8 from Hongtao.liu ---
(In reply to Martin Liška from comment #7)
> (In reply to Hongtao.liu from comment #6)
> > The opportunity disappear after r12-7125.
>
> Can you please install the latest contrib/gcc-git-customization.sh? Doi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
Hongtao.liu changed:
What|Removed |Added
Resolution|FIXED |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
Hongtao.liu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
--- Comment #5 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #4)
> > It is unclear why the CFG wasn't straightened out here. Is the bb commented
> > as "asm" actually asm? Then GCC will not see it is very cheap/small, yeah.
>
> "
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
--- Comment #4 from Hongtao.liu ---
> It is unclear why the CFG wasn't straightened out here. Is the bb commented
> as "asm" actually asm? Then GCC will not see it is very cheap/small, yeah.
"asm" is not inline assembly. it's BB 6 below
(not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
--- Comment #3 from Segher Boessenkool ---
Also combine could work that late in principle: it can deal with hard
registers, after all. But it would be a terrible idea. A single combine
pass is expensive enough, we don't want to run it N times.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
--- Comment #2 from rsandifo at gcc dot gnu.org
---
fwprop should at least stand a chance of working that late.
Was wondering whether reinitialising the loop info would be
a problem, but we already do that later (when computing
alignments).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
Richard Biener changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org,
