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/110987] [13/14 Regression] Segmentation fault after finalization of a temporary variable
Date: Fri, 29 Mar 2024 07:23:33 +0000	[thread overview]
Message-ID: <bug-110987-4-r42HjcU5sA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110987-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110987

--- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>:

https://gcc.gnu.org/g:3c793f0361bc66d2a6bf0b3e1fb3234fc511e2a6

commit r14-9719-g3c793f0361bc66d2a6bf0b3e1fb3234fc511e2a6
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Fri Mar 29 07:23:19 2024 +0000

    Fortran: Fix a gimplifier ICE/wrong result with finalization [PR36337]

    2024-03-29  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/36337
            PR fortran/110987
            PR fortran/113885
            * trans-expr.cc (gfc_trans_assignment_1): Place finalization
            block before rhs post block for elemental rhs.
            * trans.cc (gfc_finalize_tree_expr): Check directly if a type
            has no components, rather than the zero components attribute.
            Treat elemental zero component expressions in the same way as
            scalars.

    gcc/testsuite/
            PR fortran/113885
            * gfortran.dg/finalize_54.f90: New test.
            * gfortran.dg/finalize_55.f90: New test.

    gcc/testsuite/
            PR fortran/110987
            * gfortran.dg/finalize_56.f90: New test.

  parent reply	other threads:[~2024-03-29  7:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  9:11 [Bug fortran/110987] New: " chilikin.k at gmail dot com
2023-08-11  9:12 ` [Bug fortran/110987] " chilikin.k at gmail dot com
2023-08-31 18:51 ` chilikin.k at gmail dot com
2023-12-09 13:27 ` chilikin.k at gmail dot com
2024-02-04 20:51 ` anlauf at gcc dot gnu.org
2024-02-05 15:37 ` jhaiduce at gmail dot com
2024-02-05 15:54 ` jhaiduce at gmail dot com
2024-02-05 17:27 ` [Bug fortran/110987] [13/14 Regression] " anlauf at gcc dot gnu.org
2024-02-05 17:34 ` anlauf at gcc dot gnu.org
2024-03-22 13:40 ` law at gcc dot gnu.org
2024-03-28 15:59 ` pault at gcc dot gnu.org
2024-03-29  7:23 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-23  9:47 ` [Bug fortran/110987] [13 " pault at gcc dot gnu.org
2024-05-06  9:47 ` cvs-commit at gcc dot gnu.org
2024-05-06  9:50 ` 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-110987-4-r42HjcU5sA@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).