public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhroma at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/100554] [9/10/11/12 Regression] -fcompare-debug failure w/ -Os -fmodulo-sched -fno-tree-loop-optimize
Date: Wed, 19 May 2021 10:10:28 +0000 [thread overview]
Message-ID: <bug-100554-4-HJgNCMW41L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100554-4@http.gcc.gnu.org/bugzilla/>
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.
next prev parent reply other threads:[~2021-05-19 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 3:14 [Bug rtl-optimization/100554] New: " asolokha at gmx dot com
2021-05-12 7:22 ` [Bug rtl-optimization/100554] " rguenth at gcc dot gnu.org
2021-05-19 10:10 ` zhroma at gcc dot gnu.org [this message]
2021-06-01 8:20 ` rguenth at gcc dot gnu.org
2022-01-17 14:49 ` rguenth at gcc dot gnu.org
2022-05-27 9:45 ` [Bug rtl-optimization/100554] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:45 ` jakub at gcc dot gnu.org
2023-07-07 10:39 ` [Bug rtl-optimization/100554] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-11 3:38 ` law at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100554-4-HJgNCMW41L@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).