public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95947] PACK intrinsic returns blank strings when an allocatable character array with allocatable length is used
Date: Tue, 18 Jul 2023 18:45:08 +0000	[thread overview]
Message-ID: <bug-95947-4-UOS9B4d7Vv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95947-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |anlauf at gcc dot gnu.org
         Resolution|---                         |FIXED

--- Comment #9 from anlauf at gcc dot gnu.org ---
Fixed on mainline for gcc-14 so far, and on 13-branch.
Might be backported further after waiting some time.

Thanks for the report!

  parent reply	other threads:[~2023-07-18 18:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 14:28 [Bug fortran/95947] New: " urbanjost at comcast dot net
2020-06-28 14:34 ` [Bug fortran/95947] " urbanjost at comcast dot net
2020-06-28 21:20 ` urbanjost at comcast dot net
2020-07-07 13:48 ` dominiq at lps dot ens.fr
2022-12-14 14:39 ` urbanjost at comcast dot net
2022-12-14 20:28 ` anlauf at gcc dot gnu.org
2022-12-14 20:54 ` 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
2023-07-18 18:45 ` anlauf 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

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-95947-4-UOS9B4d7Vv@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).