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/107075] ICE in get, at cgraph.h:461
Date: Thu, 29 Sep 2022 21:16:33 +0000 [thread overview]
Message-ID: <bug-107075-4-x9xIsK0lbv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107075-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107075
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #3)
> (In reply to Richard Biener from comment #2)
> >
> > But maybe 'z' shouldn't be of static storage duration ...
>
> No, I think it shouldn't. A should be static, and Z should not.
Well, I think the declaration
integer, pointer :: z => a(2)
makes pointer z IMPLICIT_SAVE. At least I couldn't find anything in the
standard that makes an exception for declarations in a BLOCK construct.
This is confirmed by Intel and Cray and by replacing 'program p'
by 'subroutine p'. And in line with gfortran...
Error: Pointer initialization target at (1) must have the SAVE attribute
next prev parent reply other threads:[~2022-09-29 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 17:36 [Bug fortran/107075] New: " gscfq@t-online.de
2022-09-28 20:13 ` [Bug fortran/107075] " anlauf at gcc dot gnu.org
2022-09-29 8:17 ` rguenth at gcc dot gnu.org
2022-09-29 9:05 ` mikael at gcc dot gnu.org
2022-09-29 21:16 ` anlauf at gcc dot gnu.org [this message]
2022-10-06 18:02 ` anlauf at gcc dot gnu.org
2022-10-06 19:19 ` 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-107075-4-x9xIsK0lbv@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).