public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/95706] New test case gfortran.dg/pr95690.f90 fails
Date: Wed, 17 Jun 2020 14:56:16 +0000 [thread overview]
Message-ID: <bug-95706-4-l1vYkNzXYo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95706-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95706
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 17 Jun 2020, seurer at linux dot vnet.ibm.com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95706
>
> --- Comment #2 from Bill Seurer <seurer at linux dot vnet.ibm.com> ---
> No idea, sorry. Is that the problem? Supposed to be an error but on a
> different line?
Yes. On line 5, see the dg-error marker.
next prev parent reply other threads:[~2020-06-17 14:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 18:06 [Bug testsuite/95706] New: " seurer at linux dot vnet.ibm.com
2020-06-17 6:32 ` [Bug testsuite/95706] " rguenth at gcc dot gnu.org
2020-06-17 14:54 ` seurer at linux dot vnet.ibm.com
2020-06-17 14:56 ` rguenther at suse dot de [this message]
2020-06-18 14:24 ` clyon at gcc dot gnu.org
2020-06-25 11:06 ` rguenth at gcc dot gnu.org
2020-06-25 11:06 ` rguenth at gcc dot gnu.org
2020-07-02 6:42 ` rguenth at gcc dot gnu.org
2020-07-02 7:02 ` rguenth at gcc dot gnu.org
2020-07-02 9:21 ` rguenth at gcc dot gnu.org
2020-07-02 21:08 ` ro at gcc dot gnu.org
2020-07-02 21:17 ` dje at gcc dot gnu.org
2020-07-03 10:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-12-14 16:33 ` danglin at gcc dot gnu.org
2023-04-02 15:41 ` danglin at gcc dot gnu.org
2023-04-29 16:35 ` vital.had at gmail 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-95706-4-l1vYkNzXYo@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).