public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91726] [8/9 Regression] ICE in gfc_conv_array_ref, at fortran/trans-array.c:3612
Date: Fri, 08 Jan 2021 18:40:59 +0000 [thread overview]
Message-ID: <bug-91726-4-vIKy3oSPnY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91726-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91726
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to José Rui Faustino de Sousa from comment #7)
> Hi all!
>
> Still ICEs with 9/10/11 using -ftrapv -fcheck=bounds
>
> Best regards,
> José Rui
Yes, indeed. This with those compile options
module m
type s
class(*), allocatable :: a[:] ! This ICEd
end type
end
gives
../pr91726/pr91726.f90:5:3:
5 | end
| ^
Error: mismatching comparison operand types
integer(kind=8)
unsigned long
if (_10 != 1) goto <D.4205>; else goto <D.4206>;
../pr91726/pr91726.f90:5:3: internal compiler error: ‘verify_gimple’ failed
0xec247d verify_gimple_in_seq(gimple*)
../../gcc/gcc/tree-cfg.c:5119
The problem appears to lie in the bounds checking in
trans-expr.c(gfc_copy_class_to_class) at line 1425 in master. It is produced by
the vtable _copy function.
For some reason that I cannot see from the code, 10-branch compiles this
snippet just fine, while 9-branch produces a completely different error.
It's now in my spreadsheet as an intersting one!
Paul
next prev parent reply other threads:[~2021-01-08 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91726-4@http.gcc.gnu.org/bugzilla/>
2020-05-06 13:14 ` jrfsousa at gmail dot com
2021-01-08 18:40 ` pault at gcc dot gnu.org [this message]
2021-04-01 18:19 ` jrfsousa at gmail dot com
2021-05-14 9:52 ` [Bug fortran/91726] [9 " jakub at gcc dot gnu.org
2021-06-01 8:15 ` rguenth at gcc dot gnu.org
2022-05-27 8:38 ` 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-91726-4-vIKy3oSPnY@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).