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/102582] allocate treats all variables as type CHARACTER after use of CHARACTER(LEN=NNN)::
Date: Mon, 04 Oct 2021 01:34:28 +0000	[thread overview]
Message-ID: <bug-102582-4-JQl109ta4r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102582-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from urbanjost at comcast dot net ---
Never mind. It looks like

C934 (R927) If type-spec appears, it shall specify a type with which each
allocate-object is type compatible.

it should do that, and nvfortran and ifort are the ones doing it incorrrectly.
If that does mean gfortran is correct, feel free to to close this; but I would
like someone to concur before I close this.

It worked as I expected with two other compilers :>

  reply	other threads:[~2021-10-04  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04  0:59 [Bug fortran/102582] New: " urbanjost at comcast dot net
2021-10-04  1:34 ` urbanjost at comcast dot net [this message]
2021-10-05 19:58 ` [Bug fortran/102582] " 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-102582-4-JQl109ta4r@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).