public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96839] gfortran thinks common_bits starts a common block Date: Sat, 29 Aug 2020 14:17:03 +0000 [thread overview] Message-ID: <bug-96839-4-SCjuuxt2zJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96839-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96839 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Priority|P3 |P4 Ever confirmed|0 |1 Last reconfirmed| |2020-08-29 --- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- With GCC10 and 11 the errors are pr96839.f90:47:38: 47 | common_bits = min(self % bits, set2 % bits) | 1 Error: Expected argument list at (1) pr96839.f90:57:25: 57 | bits = self % bits | 1 Error: Expected argument list at (1) pr96839.f90:25:17: 25 | procedure, pass(self) :: bits | 1 Error: Procedure 'bits' at (1) has the same name as a component of 'bitset_t' With GCC7 to GCC9 the first error is replaced with pr96839.f90:47:14: 47 | common_bits = min(self % bits, set2 % bits) | 1 Error: Syntax error in COMMON statement at (1) Could this PR be considered as FIXED?
next prev parent reply other threads:[~2020-08-29 14:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-28 21:13 [Bug fortran/96839] New: " w.clodius at icloud dot com 2020-08-29 14:17 ` dominiq at lps dot ens.fr [this message] 2020-08-29 15:13 ` [Bug fortran/96839] " 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-SCjuuxt2zJ@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).