public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "philippe.wautelet at aero dot obs-mip.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106065] New: Crash when reading extended derived type array in namelist
Date: Thu, 23 Jun 2022 13:31:34 +0000 [thread overview]
Message-ID: <bug-106065-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106065
Bug ID: 106065
Summary: Crash when reading extended derived type array in
namelist
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: philippe.wautelet at aero dot obs-mip.fr
Target Milestone: ---
Created attachment 53195
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53195&action=edit
Reproducer
I get a crash when using an array of extended derived types.
If I define an other type containing the same information but not extended, the
problem disappears.
See the attached source:
> gfortran type_extends_nml.f90 ;./a.out
&NAM_BAL_NE
DATE_TIME_NE(1)%NYEAR= 2022,
DATE_TIME_NE(1)%NMONTH= 0,
DATE_TIME_NE(1)%NDAY= 0,
DATE_TIME_NE(1)%XTIME= 0.00000000 ,
DATE_TIME_NE(2)%NYEAR= 0,
DATE_TIME_NE(2)%NMONTH= 0,
DATE_TIME_NE(2)%NDAY= 0,
DATE_TIME_NE(2)%XTIME= 1.23399997 ,
/
At line 36 of file type_extends_nml.f90
Fortran runtime error: Cannot match namelist object name 2022
I tested with several versions of gfortran from version 5.5.0 to 12.1.0. All
failed.
next reply other threads:[~2022-06-23 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 13:31 philippe.wautelet at aero dot obs-mip.fr [this message]
2022-06-24 2:03 ` [Bug fortran/106065] " jvdelisle at gcc dot gnu.org
2022-07-02 17:22 ` jvdelisle at gcc dot gnu.org
2023-08-31 13:07 ` philippe.wautelet at aero dot obs-mip.fr
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-106065-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).