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/97272] Wrong answer from MAXLOC with character arg
Date: Thu, 08 Oct 2020 16:55:35 +0000 [thread overview]
Message-ID: <bug-97272-4-cx91n2DZBV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97272-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:d4ec0a15afb7538247206aa9936071544fd860f8
commit r10-8870-gd4ec0a15afb7538247206aa9936071544fd860f8
Author: Harald Anlauf <anlauf@gmx.de>
Date: Sun Oct 4 20:24:29 2020 +0200
PR fortran/97272 - Wrong answer from MAXLOC with character arg
The optional KIND argument to the MINLOC/MAXLOC intrinsic must not be
passed to the library function, as the kind conversion of the result
is treated explicitly elsewhere.
gcc/fortran/ChangeLog:
PR fortran/97272
* trans-intrinsic.c (strip_kind_from_actual): Helper function for
removal of KIND argument.
(gfc_conv_intrinsic_minmaxloc): Ignore KIND argument here, as it
is treated elsewhere.
gcc/testsuite/ChangeLog:
PR fortran/97272
* gfortran.dg/pr97272.f90: New test.
(cherry picked from commit 35d2c6b6e8a7448a84abbf967feeb78a29117014)
next prev parent reply other threads:[~2020-10-08 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 14:03 [Bug fortran/97272] New: " longb at cray dot com
2020-10-02 19:44 ` [Bug fortran/97272] " anlauf at gcc dot gnu.org
2020-10-02 20:02 ` anlauf at gcc dot gnu.org
2020-10-02 20:32 ` anlauf at gcc dot gnu.org
2020-10-04 18:24 ` cvs-commit at gcc dot gnu.org
2020-10-04 21:53 ` longb at cray dot com
2020-10-05 7:16 ` anlauf at gcc dot gnu.org
2020-10-08 16:55 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-08 20:29 ` cvs-commit at gcc dot gnu.org
2020-10-08 21:00 ` anlauf at gcc dot gnu.org
2021-01-22 21:08 ` longb at cray dot com
2021-01-22 21:24 ` 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-97272-4-cx91n2DZBV@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).