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/114815] [PDT] internal compiler error: Segmentation fault - on creating type with len parameter and dependent on it character array
Date: Wed, 24 Apr 2024 20:45:16 +0000 [thread overview]
Message-ID: <bug-114815-4-anbNeytBBW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114815-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114815
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to anlauf from comment #2)
> The code in comment#0 is invalid.
>
> Intel:
>
> pr114815.f90(5): error #8737: For a default initialized component every type
> parameter and array bound must be a constant expression. [GENDERS]
> end type Student_Group
> ^
>
> NAG:
>
> Error: pr114815.f90, line 4: Type STUDENT_GROUP default-initialised
> component GENDERS has a non-constant array bound
> Errors in declarations, no further processing for LAB_1_4
>
>
> When commenting the default initialization, the code compiles with gfortran.
My first project once 14-branch is released will be to put PDTs to rights.
Unfortunately, the representation is plain wrong and I don't see any point in
cosmetic fixes until that is put right.
Sorry
Paul
prev parent reply other threads:[~2024-04-24 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 23:35 [Bug fortran/114815] New: internal compiler error: Segmentation fault - Segmentation Fault " dencraft29 at gmail dot com
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 ` pault at gcc dot gnu.org [this message]
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-anbNeytBBW@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).