public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dencraft29 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/114815] New: internal compiler error: Segmentation fault - Segmentation Fault - on creating type with len parameter and dependent on it character array
Date: Mon, 22 Apr 2024 23:35:57 +0000 [thread overview]
Message-ID: <bug-114815-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114815
Bug ID: 114815
Summary: internal compiler error: Segmentation fault -
Segmentation Fault - on creating type with len
parameter and dependent on it character array
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: dencraft29 at gmail dot com
Target Milestone: ---
The following code lets gfortran crash:
program lab_1_4
type Student_Group(Size)
integer, len :: Size
character :: Genders(Size) = ""
end type Student_Group
type(Student_Group(22)) :: Group
end program lab_1_4
I have this crash on both my systems:
- GNU Fortran 12.2.0 on Debian 12 (bookworm) 6.1.0.-17-amd64 (virtual machine)
- GNU Fortran 13.2.0 on MacOS on Apple M1 Sonoma 14.4.1 (Homebrew GCC 13.2.0)
When I compile file with provided code, it consistently results in a
segmentation fault. It doesn’t matter what compilation flags I set, it
reproduced always.
Compiler stacktrace:
internal compiler error: Segmentation fault
0x1a22ff6 internal_error(char const*, ...)
???:0
0x7ad551 bool wi::lts_p<generic_wide_int<wi::extended_tree<576> >,
generic_wide_int<wi::extended_tree<576> >
>(generic_wide_int<wi::extended_tree<576> > const&,
generic_wide_int<wi::extended_tree<576> > const&)
???:0
0x7ace97 gfc_conv_array_initializer(tree_node*, gfc_expr*)
???:0
0x7d5cab gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
???:0
0x7d6280 gfc_conv_structure(gfc_se*, gfc_expr*, int)
???:0
0x7d5e47 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
???:0
0x7bfdc8 gfc_generate_function_code(gfc_namespace*)
???:0
0x7388e6 gfc_parse_file()
???:0
next reply other threads:[~2024-04-22 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 23:35 dencraft29 at gmail dot com [this message]
2024-04-23 1:15 ` [Bug fortran/114815] internal compiler error: Segmentation fault " kargls at comcast dot net
2024-04-24 20:03 ` anlauf at gcc dot gnu.org
2024-04-24 20:45 ` [Bug fortran/114815] [PDT] " 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-114815-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).