public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/94853] [10/11/12 regression] excess errors in gfortran.dg/analyzer/pr93993.f90 since r10-8012
Date: Tue, 05 Oct 2021 22:54:43 +0000 [thread overview]
Message-ID: <bug-94853-4-XElDR8tRNJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94853-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94853
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bergner at gcc dot gnu.org
--- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #4)
> Nay progress on this please?
This still seems to be broken on GCC10 over a year after Martin's ping.
next prev parent reply other threads:[~2021-10-05 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 17:03 [Bug testsuite/94853] New: [10 " seurer at linux dot vnet.ibm.com
2020-04-29 17:19 ` [Bug testsuite/94853] " jakub at gcc dot gnu.org
2020-04-30 6:43 ` rguenth at gcc dot gnu.org
2020-05-01 15:19 ` [Bug testsuite/94853] [10/11 " ro at gcc dot gnu.org
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-06-03 7:23 ` marxin at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2021-01-14 8:40 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-05-04 12:31 ` [Bug testsuite/94853] [10/11/12 " rguenth at gcc dot gnu.org
2021-10-05 22:54 ` bergner at gcc dot gnu.org [this message]
2022-06-28 10:40 ` [Bug testsuite/94853] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug testsuite/94853] [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-94853-4-XElDR8tRNJ@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).