public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/94340] [9/10 Regression] -fcompare-debug -O failure on cpp1z/nodiscard3.C
Date: Thu, 26 Mar 2020 10:31:11 +0000 [thread overview]
Message-ID: <bug-94340-4-JYgcH7XiPB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94340-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94340
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-03-26
Ever confirmed|0 |1
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |9.4
Status|UNCONFIRMED |NEW
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r9-3352-g87bd153645f393a1fe18e4fcd7f4323f83a8ac87 (which means it
has been latent before).
next prev parent reply other threads:[~2020-03-26 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 10:16 [Bug debug/94340] New: " zhroma at gcc dot gnu.org
2020-03-26 10:31 ` jakub at gcc dot gnu.org [this message]
2020-03-26 10:39 ` [Bug debug/94340] [8/9/10 " jakub at gcc dot gnu.org
2020-04-01 7:47 ` rguenth at gcc dot gnu.org
2021-05-14 9:53 ` [Bug debug/94340] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:17 ` rguenth at gcc dot gnu.org
2021-09-20 8:14 ` pinskia at gcc dot gnu.org
2022-05-27 9:42 ` [Bug debug/94340] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug debug/94340] [11/12/13/14 " 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-94340-4-JYgcH7XiPB@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).