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/100245] ICE on automatic reallocation
Date: Fri, 16 Sep 2022 19:06:32 +0000	[thread overview]
Message-ID: <bug-100245-4-qzdTvYGYlA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100245-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:9035eaaf028ca609660f1f55c0d9f22fb7d3b797

commit r12-8768-g9035eaaf028ca609660f1f55c0d9f22fb7d3b797
Author: José Rui Faustino de Sousa <jrfsousa@gmail.com>
Date:   Fri Sep 2 21:35:22 2022 +0200

    Fortran: Fix ICE with automatic reallocation [PR100245]

    gcc/fortran/ChangeLog:

            PR fortran/100245
            * trans-expr.cc (trans_class_assignment): Add if clause to handle
            derived type in the LHS.

    gcc/testsuite/ChangeLog:

            PR fortran/100245
            * gfortran.dg/PR100245.f90: New test.

    (cherry picked from commit 504424f33771be0405454e7845219d5df1bb88bb)

  parent reply	other threads:[~2022-09-16 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 11:02 [Bug fortran/100245] New: " jrfsousa at gmail dot com
2021-04-24 11:23 ` [Bug fortran/100245] " dominiq at lps dot ens.fr
2021-04-25 13:54 ` jrfsousa at gmail dot com
2021-06-18 10:59 ` dominiq at lps dot ens.fr
2022-09-01 23:36 ` jrfsousa at gcc dot gnu.org
2022-09-03 18:57 ` cvs-commit at gcc dot gnu.org
2022-09-16 19:06 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-24 19:00 ` cvs-commit at gcc dot gnu.org
2022-09-24 19:01 ` cvs-commit at gcc dot gnu.org
2022-09-24 19:02 ` 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-100245-4-qzdTvYGYlA@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).