https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100554
Roman Zhuykov <zhroma at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=100533,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=100523
CC| |abel at ispras dot ru,
| |jakub at redhat dot com,
| |zhroma at gcc dot gnu.org
--- Comment #1 from Roman Zhuykov <zhroma at gcc dot gnu.org> ---
> Is it an issue at all?
> Should I report more issues of this kind in the future?
I think the answer is "yes" for both questions, thanks for your reports!
A year ago when I bothered about regtesting with -fcompare-debug I've created a
few issues unrelated to modulo scheduler and Jakub fixed most of them. Short
summary is available at
https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542389.html, there I've
also investigated everything on modulo sched side, but small patch2.txt was
never committed.
Given now we are in stage1 and have three PRs (I'll check PR100533 and
PR100523, they should be same), now it's time to push that.
