public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ludovic@ludovic-brenta.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/95664] generic instantiation fails to detect abstract equality, builds with gcc-9 and fails to link with gcc-10 Date: Sat, 13 Jun 2020 16:01:33 +0000 [thread overview] Message-ID: <bug-95664-4-XUXPmx0ECr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95664-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95664 Ludovic Brenta <ludovic@ludovic-brenta.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ludovic@ludovic-brenta.org --- Comment #1 from Ludovic Brenta <ludovic@ludovic-brenta.org> --- ARM 3.9.3(3/2): A subprogram declared by an abstract_subprogram_declaration or a formal_abstract_subprogram_declaration is an abstract subprogram. If it is a primitive subprogram of a tagged type, then the tagged type shall be abstract. so this does not explicitly forbid abstract subprograms that are primitive to an untagged type; however: 7 A call on an abstract subprogram shall be a dispatching call; nondispatching calls to an abstract subprogram are not allowed. this implicitly requires the formal type of the controlling operand to be tagged and the actual to be class-wide. Therefore I think gcc-9.3 and gcc-10.1 should both report an error; it should be illegal to declare "=" as an abstract primitive subprogram of the untagged type Element.
next prev parent reply other threads:[~2020-06-13 16:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-13 13:42 [Bug ada/95664] New: " nicolas at debian dot org 2020-06-13 16:01 ` ludovic@ludovic-brenta.org [this message] 2020-06-14 5:21 ` [Bug ada/95664] " rosen at adalog dot fr 2020-06-29 11:10 ` [Bug ada/95664] link failure with abstract equality operator ebotcazou 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-95664-4-XUXPmx0ECr@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).