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/108450] [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380 since r12-5793-g689407ef916503b2
Date: Sun, 05 Feb 2023 21:53:33 +0000	[thread overview]
Message-ID: <bug-108450-4-F7uQ1UjHqX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108450-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Mikael Morin
<mikael@gcc.gnu.org>:

https://gcc.gnu.org/g:32502d82a5b54ca5b8e524df9fcad851727dc54a

commit r12-9108-g32502d82a5b54ca5b8e524df9fcad851727dc54a
Author: Mikael Morin <mikael@gcc.gnu.org>
Date:   Sun Jan 29 21:57:24 2023 +0100

    fortran: Set name for *LOC default BACK argument [PR108450]

    This change fixes an ICE caused by the double resolution of MINLOC,
    MAXLOC and FINDLOC expressions which get a default value for the BACK
    argument at resolution time.  That argument  is added without name,
    and argument reordering code is not prepared to handle unnamed arguments
    coming after named ones, so the second resolution causes a NULL pointer
    dereference.
    The problem is fixed by explicitly setting the argument name.

            PR fortran/108450

    gcc/fortran/ChangeLog:

            * check.cc (gfc_check_minloc_maxloc): Explicitly set argument name.
            (gfc_check_findloc): Ditto.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/gomp/minmaxloc_1.f90: New test.

    (cherry picked from commit 2e32a12c04c72f692a7bd119fd3e4e5b74392c9d)

  parent reply	other threads:[~2023-02-05 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 18:23 [Bug fortran/108450] New: [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380 gscfq@t-online.de
2023-01-19  7:47 ` [Bug fortran/108450] " rguenth at gcc dot gnu.org
2023-01-19 14:16 ` [Bug fortran/108450] [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380 since r12-5793-g689407ef916503b2 marxin at gcc dot gnu.org
2023-01-20 18:03 ` burnus at gcc dot gnu.org
2023-01-29 19:47 ` mikael at gcc dot gnu.org
2023-01-29 20:57 ` cvs-commit at gcc dot gnu.org
2023-02-05 21:53 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-05 22:22 ` mikael 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-108450-4-F7uQ1UjHqX@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).