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/110658] MINVAL/MAXVAL and deferred-length character arrays Date: Tue, 18 Jul 2023 18:40:28 +0000 [thread overview] Message-ID: <bug-110658-4-TW4N5DG3JC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110658-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110658 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:ccf94ab2abb6969c04d51c7879f07edfbb97ae55 commit r13-7584-gccf94ab2abb6969c04d51c7879f07edfbb97ae55 Author: Harald Anlauf <anlauf@gmx.de> Date: Sun Jul 16 22:17:27 2023 +0200 Fortran: intrinsics and deferred-length character arguments [PR95947,PR110658] gcc/fortran/ChangeLog: PR fortran/95947 PR fortran/110658 * trans-expr.cc (gfc_conv_procedure_call): For intrinsic procedures whose result characteristics depends on the first argument and which can be of type character, the character length will not be deferred. gcc/testsuite/ChangeLog: PR fortran/95947 PR fortran/110658 * gfortran.dg/deferred_character_37.f90: New test. (cherry picked from commit 95ddd2659849a904509067ec3a2770135149a722)
next prev parent reply other threads:[~2023-07-18 18:40 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-13 18:26 [Bug fortran/110658] New: " anlauf at gcc dot gnu.org 2023-07-16 19:34 ` [Bug fortran/110658] " anlauf at gcc dot gnu.org 2023-07-16 20:31 ` anlauf at gcc dot gnu.org 2023-07-17 18:49 ` cvs-commit at gcc dot gnu.org 2023-07-18 18:40 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-20 18:56 ` cvs-commit at gcc dot gnu.org 2023-07-20 19:06 ` cvs-commit at gcc dot gnu.org 2023-07-20 19:06 ` 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-110658-4-TW4N5DG3JC@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: linkBe 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).