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 tree-optimization/105665] [12/13 Regression] wrong code at -Os and above on x86_64-linux-gnu since r12-397-gda9e6e63d1ae22
Date: Sun, 22 May 2022 02:32:42 +0000 [thread overview]
Message-ID: <bug-105665-4-N22BLl5oEV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105665-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105665
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> Started with r12-398-g5fbe6a8e73b52c6ebc28b9 because r12-397 didn't compile,
> but yes, it is r12-397.
And it is very similar to PR 100810 in the sense there is an not-executed use
of an uninitialized variable too.
next prev parent reply other threads:[~2022-05-22 2:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 20:19 [Bug tree-optimization/105665] New: wrong code at -Os and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2022-05-19 20:20 ` [Bug tree-optimization/105665] " zhendong.su at inf dot ethz.ch
2022-05-19 20:26 ` [Bug tree-optimization/105665] [12/13 Regression] wrong code at -Os and above on x86_64-linux-gnu since r12-397-gda9e6e63d1ae22 marxin at gcc dot gnu.org
2022-05-19 21:04 ` jakub at gcc dot gnu.org
2022-05-20 6:42 ` rguenth at gcc dot gnu.org
2022-05-22 2:32 ` pinskia at gcc dot gnu.org [this message]
2022-05-28 0:17 ` aoliva at gcc dot gnu.org
2022-06-03 7:05 ` cvs-commit at gcc dot gnu.org
2022-07-27 9:24 ` [Bug tree-optimization/105665] [12 " cvs-commit at gcc dot gnu.org
2022-07-27 9:24 ` rguenth 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-105665-4-N22BLl5oEV@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).