public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107142] New: [PDT] ICE: Segmentation fault (in next_statement)
Date: Tue, 04 Oct 2022 04:22:56 +0000 [thread overview]
Message-ID: <bug-107142-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107142
Bug ID: 107142
Summary: [PDT] ICE: Segmentation fault (in next_statement)
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-invalid-code
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gfortran 13.0.0 20220925 snapshot (g:77bbf69d2981dafc2ef3e59bfbefb645d88bab9d)
ICEs when compiling the following testcase, reduced from
test/Semantics/selecttype01.f90 from the flang 15.0.1 test suite:
module c1162a
type pdt(kind,len)
integer, kind :: kind
integer, len :: len
end type
contains
subroutine foo(x)
class(pdt(kind=1,len=:)), allocatable :: x
select type (x)
type is (pdt(kind=*, len=*))
end select
end subroutine
end module
% gfortran-13.0.0 -c lwe7niqj.f90
lwe7niqj.f90:10:14:
10 | type is (pdt(kind=*, len=*))
| 1
Error: Syntax error in TYPE IS specification at (1)
f951: internal compiler error: Segmentation fault
0xf756bf crash_signal
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/toplev.cc:314
0x928173 next_statement
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/fortran/parse.cc:1608
0x92bed0 parse_executable
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/fortran/parse.cc:5968
0x92dc90 parse_progunit
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/fortran/parse.cc:6238
0x92e094 parse_contained
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/fortran/parse.cc:6113
0x92f025 parse_module
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/fortran/parse.cc:6486
0x92f468 gfc_parse_file()
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/fortran/parse.cc:6793
0x98248f gfc_be_parse_file
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/fortran/f95-lang.cc:229
next reply other threads:[~2022-10-04 4:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 4:22 asolokha at gmx dot com [this message]
2023-06-30 8:51 ` [Bug fortran/107142] " pault at gcc dot gnu.org
2023-06-30 8:52 ` pault 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-107142-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).