public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107397] [11/12 Regression] ICE in gfc_arith_plus, at fortran/arith.cc:654
Date: Sun, 06 Aug 2023 00:34:14 +0000 [thread overview]
Message-ID: <bug-107397-4-OKWfJaVSns@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107397-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107397
--- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Jerry DeLisle
<jvdelisle@gcc.gnu.org>:
https://gcc.gnu.org/g:a3931bf6093dbeda637601da07cdbbd07e57ccbd
commit r12-9802-ga3931bf6093dbeda637601da07cdbbd07e57ccbd
Author: Jakub Jelinek <jakub@redhat.com>
Date: Mon Dec 19 11:24:55 2022 +0100
testsuite: Fix up pr107397.f90 test [PR107397]
The pr107397.f90 test FAILs for me, one problem was that the
added diagnostics has an indefinite article before BOZ, but
the test dg-error didn't. The other problem was that on the
other dg-error there was no space between the string and closing
}, so it was completely ignored and the error was an excess
error.
2022-12-19 Jakub Jelinek <jakub@redhat.com>
PR fortran/107397
* gfortran.dg/pr107397.f90: Adjust expected diagnostic wording and
add space between dg-error string and closing }.
(cherry picked from commit 03fb35f8753d87148b29b3f34b6154abe7db4c41)
next prev parent reply other threads:[~2023-08-06 0:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 17:29 [Bug fortran/107397] New: [10/11/12/13 " gscfq@t-online.de
2022-10-25 18:21 ` [Bug fortran/107397] " anlauf at gcc dot gnu.org
2022-10-25 19:31 ` marxin at gcc dot gnu.org
2022-10-26 14:07 ` kargl at gcc dot gnu.org
2022-10-28 11:12 ` rguenth at gcc dot gnu.org
2022-10-28 20:31 ` anlauf at gcc dot gnu.org
2022-10-28 21:43 ` sgk at troutmask dot apl.washington.edu
2022-10-28 21:51 ` anlauf at gcc dot gnu.org
2022-10-29 19:09 ` anlauf at gcc dot gnu.org
2022-12-18 3:39 ` cvs-commit at gcc dot gnu.org
2022-12-18 12:18 ` rimvydas.jas at gmail dot com
2022-12-18 12:19 ` rimvydas.jas at gmail dot com
2022-12-19 10:35 ` cvs-commit at gcc dot gnu.org
2023-01-17 20:49 ` [Bug fortran/107397] [10/11/12 " anlauf at gcc dot gnu.org
2023-07-07 10:44 ` [Bug fortran/107397] [11/12 " rguenth at gcc dot gnu.org
2023-07-07 20:30 ` anlauf at gcc dot gnu.org
2023-08-05 23:52 ` jvdelisle at gcc dot gnu.org
2023-08-06 0:34 ` cvs-commit at gcc dot gnu.org
2023-08-06 0:34 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-06 0:54 ` cvs-commit at gcc dot gnu.org
2023-08-06 0:54 ` cvs-commit at gcc dot gnu.org
2023-08-06 1:04 ` jvdelisle 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-107397-4-OKWfJaVSns@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).