public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "urbanjost at comcast dot net" <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: Sun, 28 Jun 2020 14:34:41 +0000 [thread overview] Message-ID: <bug-95947-4-hFAxuPd7P5@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 --- Comment #1 from urbanjost at comcast dot net --- Created attachment 48796 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48796&action=edit test using PACK(3f) intrinsic with allocatable variables PACK() intrinsic is returning all blanks in subroutine BAD3(). Expect all three test routines to produce "bat cat"; but third one produces blanks, Seems to occur only with len=: variable(?) gfortran xbad.f90 bash-4.4$ ./a.out bat cat bat cat 10 4
next prev parent reply other threads:[~2020-06-28 14:34 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 ` urbanjost at comcast dot net [this message] 2020-06-28 21:20 ` [Bug fortran/95947] " 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 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-hFAxuPd7P5@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).