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: Sun, 16 Jan 2022 18:16:22 +0000	[thread overview]
Message-ID: <bug-87711-4-HXIZFJeu7z@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 #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Mikael Morin <mikael@gcc.gnu.org>:

https://gcc.gnu.org/g:15630e6e9eb019477d1fc5c0966b43979e18ae18

commit r12-6613-g15630e6e9eb019477d1fc5c0966b43979e18ae18
Author: Mikael Morin <mikael@gcc.gnu.org>
Date:   Sun Jan 16 18:33:36 2022 +0100

    testsuite: Enrich tests with variants failing on the branch.

    Backporting the fix for pr103789 on the 11 branch revealed a lack of test
    coverage for the tests provided with that fix.  Indeed, the tests use the
KIND
    argument of the respective intrinsics only with keyword arguments.
    This adds variants with non-keyword arguments.

    The tests enriched this way fail on the branch if the fix is cherry-picked
    straightforwardly.  The fix will have to be tweaked slightly there.

            PR fortran/103789
            PR fortran/87711
            PR fortran/97896

    gcc/testsuite/ChangeLog:

            * gfortran.dg/index_5.f90: Enrich test with usages of INDEX with
            a non-keyword KIND argument.
            * gfortran.dg/len_trim.f90: Same for LEN_TRIM.
            * gfortran.dg/maskl_1.f90: Same for MASKL.
            * gfortran.dg/maskr_1.f90: Same for MASKR.
            * gfortran.dg/scan_3.f90: Same for SCAN.
            * gfortran.dg/verify_3.f90: Same for VERIFY.

  parent reply	other threads:[~2022-01-16 18:16 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
2022-01-16 18:16 ` cvs-commit at gcc dot gnu.org [this message]
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-HXIZFJeu7z@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).