public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/106032] [10/11/12/13 Regression] wrong code at -Os and above on x86_64-linux-gnu
Date: Mon, 20 Jun 2022 08:09:14 +0000 [thread overview]
Message-ID: <bug-106032-4-2yTirOSIt0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106032-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106032
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #5)
> (In reply to Andrew Pinski from comment #4)
> > Here is a testcase which shows this was latent but fails in GCC 7+ (so it is
> > still a regression):
> > int a, b, c, *d;
> > int main() {
> > int e = 0, f = 0;
> > int *dd = d;
> > for (; f < 1; f++)
> > if (c < 0)
> > e = *dd;
> > if (a) {
> > a = b ? 0 : a;
> > e && (b = a);
> > }
> > return 0;
> > }
>
> This one started with r9-6299-gd7a700e0a701e516.
I guess I need to make another testcase since that would have just changed the
gimple level.
next prev parent reply other threads:[~2022-06-20 8:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 20:52 [Bug tree-optimization/106032] New: " zhendong.su at inf dot ethz.ch
2022-06-19 20:53 ` [Bug tree-optimization/106032] " zhendong.su at inf dot ethz.ch
2022-06-19 20:57 ` [Bug tree-optimization/106032] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-06-19 21:04 ` [Bug rtl-optimization/106032] " pinskia at gcc dot gnu.org
2022-06-19 21:08 ` [Bug rtl-optimization/106032] [10/11/12/13 " pinskia at gcc dot gnu.org
2022-06-20 8:04 ` marxin at gcc dot gnu.org
2022-06-20 8:09 ` pinskia at gcc dot gnu.org [this message]
2022-06-20 11:45 ` rguenth at gcc dot gnu.org
2022-06-20 15:09 ` jakub at gcc dot gnu.org
2022-06-20 15:58 ` jakub at gcc dot gnu.org
2022-06-20 16:08 ` jakub at gcc dot gnu.org
2022-06-21 9:40 ` cvs-commit at gcc dot gnu.org
2022-06-28 10:49 ` jakub at gcc dot gnu.org
2022-06-28 15:38 ` cvs-commit at gcc dot gnu.org
2022-06-28 15:47 ` [Bug rtl-optimization/106032] [10/11 " jakub at gcc dot gnu.org
2022-11-04 8:30 ` cvs-commit at gcc dot gnu.org
2022-11-04 11:00 ` [Bug rtl-optimization/106032] [10 " jakub at gcc dot gnu.org
2023-05-03 15:18 ` cvs-commit at gcc dot gnu.org
2023-05-04 7:18 ` jakub 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-106032-4-2yTirOSIt0@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).