public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/112764] Associating entity does not have target attribute if selector has pointer attribute in associate block Date: Fri, 01 Dec 2023 05:29:25 +0000 [thread overview] Message-ID: <bug-112764-4-hfLLI8JGK4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112764-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112764 --- Comment #10 from martin <mscfd at gmx dot net> --- Thanks for the speedy fix! I just thought about a variation, which should now with the fix work as well (was not yet able to compile current dev branch, so cannot check myself): program assoc_ptr_in implicit none integer, dimension(:,:), pointer :: x integer, pointer :: j allocate(x(1:100,1:2), source=123) associate(i1 => x(:,1)) call sub(i1) end associate deallocate(x) contains subroutine sub(j) integer, dimension(:), pointer, intent(in) :: j print *,j(1) end subroutine sub end program assoc_ptr_in
next prev parent reply other threads:[~2023-12-01 5:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-29 14:01 [Bug fortran/112764] New: " mscfd at gmx dot net 2023-11-29 18:02 ` [Bug fortran/112764] " anlauf at gcc dot gnu.org 2023-11-29 20:09 ` anlauf at gcc dot gnu.org 2023-11-29 20:10 ` anlauf at gcc dot gnu.org 2023-11-29 20:17 ` mscfd at gmx dot net 2023-11-29 20:37 ` anlauf at gcc dot gnu.org 2023-11-29 21:17 ` anlauf at gcc dot gnu.org 2023-11-30 12:38 ` cvs-commit at gcc dot gnu.org 2023-11-30 21:21 ` cvs-commit at gcc dot gnu.org 2023-11-30 21:23 ` anlauf at gcc dot gnu.org 2023-12-01 5:29 ` mscfd at gmx dot net [this message] 2023-12-01 17:52 ` 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-112764-4-hfLLI8JGK4@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).