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/106945] [10/11/12/13 Regression] ICE: 'verify_gimple' failed
Date: Fri, 10 Mar 2023 21:21:24 +0000 [thread overview]
Message-ID: <bug-106945-4-QT7YmQQ4pJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106945-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106945
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
--- Comment #4 from anlauf at gcc dot gnu.org ---
As there is no ICE with -fcheck=bounds -fwrapv but with -fcheck=bounds -ftrapv,
there might be a wrapping issue with the bounds checking code.
Difference of the dump-trees:
--- pr106945-z1.f90.005t.original.wrapv 2023-03-10 22:15:44.992525716 +0100
+++ pr106945-z1.f90.005t.original.trapv 2023-03-10 22:15:24.892582362 +0100
@@ -268,7 +268,7 @@
D.4395 = (unsigned long) src->a._vptr->_size;
D.4396 = (unsigned long) src->a._len;
D.4397 = D.4396 != 0 ? D.4395 * D.4396 : D.4395;
- if (src->a._data.dim[0].ubound != src->a._data.dim[0].lbound)
+ if ((src->a._data.dim[0].ubound - src->a._data.dim[0].lbound) + 1
!= 1)
{
_gfortran_runtime_error_at (&"At line 9 of file
pr106945-z1.f90"[1]{lb: 1 sz: 1}, &"Array bound mismatch for dimension 1 of
array \'<<unknown>>\' (%ld/%ld)"[1]{lb: 1 sz: 1}, 1, MAX_EXPR
<(src->a._data.dim[0].ubound - src->a._data.dim[0].lbound) + 1, 0>);
}
I am having difficulties to understand the code generated for -ftrapv.
next prev parent reply other threads:[~2023-03-10 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 18:52 [Bug fortran/106945] New: " gscfq@t-online.de
2022-09-14 18:52 ` [Bug fortran/106945] " gscfq@t-online.de
2022-09-14 19:58 ` marxin at gcc dot gnu.org
2022-09-15 7:18 ` rguenth at gcc dot gnu.org
2022-09-23 19:56 ` anlauf at gcc dot gnu.org
2023-03-10 21:21 ` anlauf at gcc dot gnu.org [this message]
2023-03-11 14:35 ` anlauf at gcc dot gnu.org
2023-03-11 14:52 ` cvs-commit at gcc dot gnu.org
2023-03-15 20:46 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:40 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:41 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:42 ` anlauf 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-106945-4-QT7YmQQ4pJ@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).