public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/114859] [14/15 Regression] Seeing new segmentation fault in same_type_as since r14-9752
Date: Tue, 30 Apr 2024 08:21:20 +0000 [thread overview]
Message-ID: <bug-114859-4-Xpwp1NnXaq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114859-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114859
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And now cherry-picked to 14.1 as well:
commit r14-10153-ge976bef1579086e6e83c6a47f6c5f8f996208f99
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Mon Apr 29 11:52:11 2024 +0100
Fortran: Fix regression caused by r14-9752 [PR114959]
2024-04-29 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/114959
* trans-expr.cc (gfc_trans_class_init_assign): Return NULL_TREE
if the default initializer has all NULL fields. Guard this
by a requirement that the code not be EXEC_INIT_ASSIGN and that
the object be an INTENT_OUT dummy.
* trans-stmt.cc (gfc_trans_allocate): Change the initializer
code for allocate with mold to EXEC_ALLOCATE to allow an
initializer with all NULL fields.
gcc/testsuite/
PR fortran/114959
* gfortran.dg/pr114959.f90: New test.
(cherry picked from commit bca41a8d55e830c882b0f39246afead4fcfae6f7)
prev parent reply other threads:[~2024-04-30 8:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 3:59 [Bug fortran/114859] New: Seeing new segmentation fault in same_type_as orion at nwra dot com
2024-04-26 7:48 ` [Bug fortran/114859] " jakub at gcc dot gnu.org
2024-04-26 7:55 ` jakub at gcc dot gnu.org
2024-04-26 8:03 ` jakub at gcc dot gnu.org
2024-04-26 15:48 ` jakub at gcc dot gnu.org
2024-04-26 16:50 ` [Bug fortran/114859] [14 Regression] Seeing new segmentation fault in same_type_as since r14-9752 jakub at gcc dot gnu.org
2024-04-26 16:55 ` jakub at gcc dot gnu.org
2024-04-26 16:59 ` jakub at gcc dot gnu.org
2024-04-26 17:10 ` jakub at gcc dot gnu.org
2024-04-26 18:07 ` [Bug fortran/114859] [14/15 " jakub at gcc dot gnu.org
2024-04-26 18:27 ` jakub at gcc dot gnu.org
2024-04-27 14:50 ` pault at gcc dot gnu.org
2024-04-27 18:58 ` jakub at gcc dot gnu.org
2024-04-28 5:37 ` pault at gcc dot gnu.org
2024-04-28 21:19 ` pault at gcc dot gnu.org
2024-04-29 9:11 ` jakub at gcc dot gnu.org
2024-04-29 11:06 ` pault at gcc dot gnu.org
2024-04-29 18:45 ` anlauf at gcc dot gnu.org
2024-04-30 8:21 ` jakub 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-114859-4-Xpwp1NnXaq@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).