public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "w.clodius at icloud dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96839] New: gfortran thinks common_bits starts a common block Date: Fri, 28 Aug 2020 21:13:05 +0000 [thread overview] Message-ID: <bug-96839-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96839 Bug ID: 96839 Summary: gfortran thinks common_bits starts a common block Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: w.clodius at icloud dot com Target Milestone: --- Created attachment 49151 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49151&action=edit A reduced code illustrating the problem. If I have both a member function named bits and an attribute named bits, a combination that is illegal, gfortran 8.1 gets confused and thinks common_bits starts a common block. It took me a while to understand the cause of the error message.
next reply other threads:[~2020-08-28 21:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-28 21:13 w.clodius at icloud dot com [this message] 2020-08-29 14:17 ` [Bug fortran/96839] " dominiq at lps dot ens.fr 2020-08-29 15:13 ` w.clodius at icloud dot com 2020-12-02 20:46 ` 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-96839-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).