public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97612] [F08] Structure constructor of type with nested allocatable array components fails to compile
Date: Fri, 10 Sep 2021 20:50:54 +0000 [thread overview]
Message-ID: <bug-97612-4-fak53tw33G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97612-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97612
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:19f2f22d59f4a3a7e246d09be11a727cffb8badc
commit r9-9722-g19f2f22d59f4a3a7e246d09be11a727cffb8badc
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Tue Dec 29 17:44:48 2020 +0000
Fortran: Correct missing structure constructor comps. [PR97612].
2020-12-29 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/97612
* primary.c (build_actual_constructor): Missing allocatable
components are set unallocated using EXPR_NULL. Then missing
components are tested for a default initializer.
gcc/testsuite/
PR fortran/97612
* gfortran.dg/structure_constructor_17.f90: New test.
(cherry picked from commit eeb145317b42d5203056851435457d9189a7303d)
next prev parent reply other threads:[~2021-09-10 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 8:51 [Bug fortran/97612] New: " mscfd at gmx dot net
2020-12-02 20:15 ` [Bug fortran/97612] " dominiq at lps dot ens.fr
2020-12-07 9:23 ` mscfd at gmx dot net
2020-12-07 12:46 ` [Bug fortran/97612] [F08] " dominiq at lps dot ens.fr
2020-12-18 12:20 ` pault at gcc dot gnu.org
2020-12-29 17:50 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2021-09-10 20:49 ` cvs-commit at gcc dot gnu.org
2021-09-10 20:50 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-10 20:52 ` anlauf 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-97612-4-fak53tw33G@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).