public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109348] New: Pointer initialization fails for target with references Date: Thu, 30 Mar 2023 18:59:49 +0000 [thread overview] Message-ID: <bug-109348-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109348 Bug ID: 109348 Summary: Pointer initialization fails for target with references Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: pault at gcc dot gnu.org Target Milestone: --- As posted by Peter Klausler on clf complex, save, target :: a(4) = [(1.,0.),(2.,0.),(3.,0.),(4.,0)] real, pointer :: p(:) => a(1:3:2)%re print *, p end gfc doesn't even attempt to initialise the pointer. Malcolm Cohen and Steve Lionel both agree that this is valid F2018. complex, save, target :: a(4) = [(1.,0.),(2.,0.),(3.,0.),(4.,0)] real, pointer :: p(:) p(1:) => a(1:3:2)%re print *, p end Works, as long as an lbound is provided on the lhs. nagfor behaves similarly, whereas ifort does not even accept this version. Cheers Paul
next reply other threads:[~2023-03-30 18:59 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-30 18:59 pault at gcc dot gnu.org [this message] 2023-03-30 19:16 ` [Bug fortran/109348] " 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-109348-4@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).