public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug fortran/102582] New: allocate treats all variables as type CHARACTER after use of CHARACTER(LEN=NNN)::
@ 2021-10-04 0:59 urbanjost at comcast dot net
2021-10-04 1:34 ` [Bug fortran/102582] " urbanjost at comcast dot net
2021-10-05 19:58 ` anlauf at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: urbanjost at comcast dot net @ 2021-10-04 0:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102582
Bug ID: 102582
Summary: allocate treats all variables as type CHARACTER after
use of CHARACTER(LEN=NNN)::
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: urbanjost at comcast dot net
Target Milestone: ---
Created attachment 51544
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51544&action=edit
example of ALLOCATE(3f) statement that fails
After an allocate of the form "ALLOCATE(CHARACTER(LEN=NNN) ::
A(10),B(10),C(10))"
all variables after "A" are treated as CHARACTER even though declared to be
other types.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug fortran/102582] allocate treats all variables as type CHARACTER after use of CHARACTER(LEN=NNN):: 2021-10-04 0:59 [Bug fortran/102582] New: allocate treats all variables as type CHARACTER after use of CHARACTER(LEN=NNN):: urbanjost at comcast dot net @ 2021-10-04 1:34 ` urbanjost at comcast dot net 2021-10-05 19:58 ` anlauf at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: urbanjost at comcast dot net @ 2021-10-04 1:34 UTC (permalink / raw) To: gcc-bugs 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 :> ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/102582] allocate treats all variables as type CHARACTER after use of CHARACTER(LEN=NNN):: 2021-10-04 0:59 [Bug fortran/102582] New: allocate treats all variables as type CHARACTER after use of CHARACTER(LEN=NNN):: urbanjost at comcast dot net 2021-10-04 1:34 ` [Bug fortran/102582] " urbanjost at comcast dot net @ 2021-10-05 19:58 ` anlauf at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: anlauf at gcc dot gnu.org @ 2021-10-05 19:58 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102582 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from anlauf at gcc dot gnu.org --- Thanks for confirming that other compilers may have bugs! Closing as per request. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-10-05 19:58 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-10-04 0:59 [Bug fortran/102582] New: allocate treats all variables as type CHARACTER after use of CHARACTER(LEN=NNN):: urbanjost at comcast dot net 2021-10-04 1:34 ` [Bug fortran/102582] " urbanjost at comcast dot net 2021-10-05 19:58 ` anlauf at gcc dot gnu.org
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).