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 testsuite/98125] [11 Regression] New test case g++.dg/pr93195a.C in r11-5656 has excess errors
Date: Tue, 23 Feb 2021 15:29:14 +0000	[thread overview]
Message-ID: <bug-98125-4-MmVE1yawOr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98125-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98125

--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
In any case, if the option is totally broken, we should either fix it for GCC
11 or emit sorry message to make it clear to users the option is not supported.

  parent reply	other threads:[~2021-02-23 15:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 16:31 [Bug testsuite/98125] New: " seurer at gcc dot gnu.org
2020-12-03 16:36 ` [Bug testsuite/98125] " hjl.tools at gmail dot com
2020-12-03 16:56 ` seurer at gcc dot gnu.org
2020-12-03 18:20 ` hjl.tools at gmail dot com
2020-12-03 20:18 ` hjl.tools at gmail dot com
2020-12-04  6:09 ` amodra at gmail dot com
2020-12-04  7:11 ` [Bug testsuite/98125] [11 Regression] " rguenth at gcc dot gnu.org
2020-12-04 12:00 ` amodra at gmail dot com
2020-12-07 21:45 ` amodra at gmail dot com
2021-01-14 11:01 ` rguenth at gcc dot gnu.org
2021-01-22 15:16 ` jakub at gcc dot gnu.org
2021-01-22 21:05 ` seurer at gcc dot gnu.org
2021-01-22 22:13 ` amodra at gmail dot com
2021-01-22 22:18 ` amodra at gmail dot com
2021-02-12 15:13 ` jakub at gcc dot gnu.org
2021-02-16  1:07 ` amodra at gmail dot com
2021-02-23 15:29 ` jakub at gcc dot gnu.org [this message]
2021-02-23 15:32 ` jakub at gcc dot gnu.org
2021-03-30 13:02 ` jakub at gcc dot gnu.org
2021-03-30 14:10 ` jakub at gcc dot gnu.org
2021-04-03  8:04 ` cvs-commit at gcc dot gnu.org
2021-04-03  8:16 ` 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-98125-4-MmVE1yawOr@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).