public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Bader at lrz dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/67744] New: polymorphic associating entity is refused TBP invocation Date: Mon, 28 Sep 2015 12:23:00 -0000 [thread overview] Message-ID: <bug-67744-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67744 Bug ID: 67744 Summary: polymorphic associating entity is refused TBP invocation Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: Bader at lrz dot de Target Milestone: --- Created attachment 36408 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36408&action=edit Fortran free form source for test case The attached test case produces following spurious compile-time error: assoc_08_pos.f90:41:10: call g%write() 1 Error: VARIABLE attribute of 'g' conflicts with PROCEDURE attribute at (1) The error persists in more recent versions (trunk).
next reply other threads:[~2015-09-28 12:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-28 12:23 Bader at lrz dot de [this message] 2015-10-10 8:23 ` [Bug fortran/67744] " dominiq at lps dot ens.fr 2015-10-12 19:14 ` Bader at lrz dot de 2015-10-12 19:15 ` Bader at lrz dot de 2015-10-13 13:11 ` dominiq at lps dot ens.fr 2021-02-13 11:53 ` [Bug fortran/67744] [OOP] " dominiq at lps dot ens.fr
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-67744-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).