public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106934] New: [10/11/12/13 Regression] ICE: verify_gimple failed
Date: Tue, 13 Sep 2022 19:32:49 +0000 [thread overview]
Message-ID: <bug-106934-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106934
Bug ID: 106934
Summary: [10/11/12/13 Regression] ICE: verify_gimple failed
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started with r9 :
(gcc configured with --enable-checking=yes)
$ cat z1.f90
subroutine s
logical(1) :: a = .true.
logical(2) :: b
a = transfer(b, a)
end
$ gfortran-13-20220911 -c z1.f90 -O2
z1.f90:5:3:
5 | end
| ^
Error: 'bit_field_ref' of non-mode-precision operand
_12 = BIT_FIELD_REF <b_13(D), 8, 0>;
during GIMPLE pass: ccp
z1.f90:5:3: internal compiler error: verify_gimple failed
0xf92e24 verify_gimple_in_cfg(function*, bool)
../../gcc/tree-cfg.cc:5569
0xe391ee execute_function_todo
../../gcc/passes.cc:2091
0xe39c72 execute_todo
../../gcc/passes.cc:2145
next reply other threads:[~2022-09-13 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 19:32 gscfq@t-online.de [this message]
2022-09-13 19:44 ` [Bug fortran/106934] " pinskia at gcc dot gnu.org
2022-09-13 20:15 ` [Bug fortran/106934] [10/11/12/13 Regression] ICE: verify_gimple failed since r9-5682-gef310a95a934d0f3 marxin at gcc dot gnu.org
2022-09-14 6:41 ` [Bug tree-optimization/106934] " rguenth at gcc dot gnu.org
2022-09-14 9:57 ` cvs-commit at gcc dot gnu.org
2022-09-14 9:58 ` [Bug tree-optimization/106934] [10/11/12 " rguenth at gcc dot gnu.org
2022-10-11 12:07 ` cvs-commit at gcc dot gnu.org
2022-10-17 13:28 ` [Bug tree-optimization/106934] [10/11 " cvs-commit at gcc dot gnu.org
2023-01-26 13:05 ` [Bug tree-optimization/106934] [10 " cvs-commit at gcc dot gnu.org
2023-01-26 13:06 ` 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-106934-4@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).