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/87711] ICE in gfc_trans_transfer, at fortran/trans-io.c:2676
Date: Wed, 24 Nov 2021 19:51:17 +0000	[thread overview]
Message-ID: <bug-87711-4-s57hZiK5Ln@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87711-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r11-9307-g3e6b9910e8e23d690fa1026b2879d37745ddd740
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Tue Nov 23 17:51:38 2021 +0100

    Fortran: fix scalarization for intrinsic LEN_TRIM with present KIND
argument

    gcc/fortran/ChangeLog:

            PR fortran/87711
            PR fortran/87851
            * trans-array.c (arg_evaluated_for_scalarization): Add LEN_TRIM to
            list of intrinsics for which an optional KIND argument needs to be
            removed before scalarization.

    gcc/testsuite/ChangeLog:

            PR fortran/87711
            PR fortran/87851
            * gfortran.dg/len_trim.f90: New test.

    (cherry picked from commit 721d8b9e26bf8205c1f2125c2626919a408cdbe4)

  parent reply	other threads:[~2021-11-24 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-87711-4@http.gcc.gnu.org/bugzilla/>
2020-08-20 20:11 ` anlauf at gcc dot gnu.org
2021-11-23 16:52 ` cvs-commit at gcc dot gnu.org
2021-11-23 16:54 ` anlauf at gcc dot gnu.org
2021-11-24 19:51 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-16 18:16 ` cvs-commit at gcc dot gnu.org
2022-01-16 21:20 ` cvs-commit at gcc dot gnu.org
2022-01-16 21:20 ` cvs-commit at gcc dot gnu.org
2023-07-07  8:17 ` rguenth 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-87711-4-s57hZiK5Ln@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).