public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101223] [11/12 Regression] evrp produces wrong code since r11-3685-gfcae5121154d1c33
Date: Mon, 28 Jun 2021 10:59:54 +0000 [thread overview]
Message-ID: <bug-101223-4-4NTaxN44ca@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101223-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101223
--- Comment #6 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> d is not an automatic variable, so is zero initialized.
Whoops. Sorry for the noise.
next prev parent reply other threads:[~2021-06-28 10:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 12:44 [Bug tree-optimization/101223] New: wrong code at -Os and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2021-06-28 2:34 ` [Bug tree-optimization/101223] [11/12 Regression] " pinskia at gcc dot gnu.org
2021-06-28 3:00 ` [Bug tree-optimization/101223] [11/12 Regression] evrp produces wrong code pinskia at gcc dot gnu.org
2021-06-28 3:03 ` pinskia at gcc dot gnu.org
2021-06-28 7:02 ` rguenth at gcc dot gnu.org
2021-06-28 7:27 ` [Bug tree-optimization/101223] [11/12 Regression] evrp produces wrong code since r11-3685-gfcae5121154d1c33 marxin at gcc dot gnu.org
2021-06-28 10:57 ` aldyh at gcc dot gnu.org
2021-06-28 10:58 ` jakub at gcc dot gnu.org
2021-06-28 10:59 ` aldyh at gcc dot gnu.org [this message]
2021-06-28 14:19 ` amacleod at redhat dot com
2021-07-02 13:03 ` rsandifo at gcc dot gnu.org
2021-07-02 13:14 ` jakub at gcc dot gnu.org
2021-07-02 13:18 ` rsandifo at gcc dot gnu.org
2021-07-02 15:35 ` cvs-commit at gcc dot gnu.org
2021-07-02 15:37 ` amacleod at redhat dot com
2021-07-02 20:31 ` [Bug tree-optimization/101223] [11 " pinskia at gcc dot gnu.org
2021-07-14 21:58 ` cvs-commit at gcc dot gnu.org
2021-07-14 22:16 ` amacleod at redhat dot com
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-101223-4-4NTaxN44ca@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).