public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103472] ICE in gfc_conv_ss_startstride, at fortran/trans-array.c:4527
Date: Sun, 12 Dec 2021 20:22:20 +0000 [thread overview]
Message-ID: <bug-103472-4-w5uRV8m89t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103472-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103472
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-12-12
Status|UNCONFIRMED |NEW
Priority|P3 |P4
Ever confirmed|0 |1
CC| |anlauf at gcc dot gnu.org
--- Comment #2 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #1)
> We could workaround it by replacing warnings with errors.
> Are there cases where we do want warnings, not errors?
I would consider the testcase as invalid, so an error appears ok.
But technically the lower bound of a is 1 and upper bound is 0,
so the error message is a bit misleading.
E.g. NAG gives:
Error: pr103472-z1.f90, line 2: First subscript (1) is greater than upper bound
(0) for array A
next prev parent reply other threads:[~2021-12-12 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 18:49 [Bug fortran/103472] New: " gscfq@t-online.de
2021-12-12 18:15 ` [Bug fortran/103472] " mikael at gcc dot gnu.org
2021-12-12 20:22 ` anlauf at gcc dot gnu.org [this message]
2024-03-21 17:58 ` mikael 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-103472-4-w5uRV8m89t@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).