public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66995] [DR317] First declaration as inline after definition of function Date: Wed, 24 Aug 2022 11:54:22 +0000 [thread overview] Message-ID: <bug-66995-4-36nlCTz063@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66995-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66995 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2021-08-04 00:00:00 |2022-8-24 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- Clang rejects this: in.C:2:13: error: inline declaration of 'f' follows non-inline definition inline void f(); ^ in.C:1:6: note: previous definition is here void f() {} ^ 1 error generated. EDG accepts it by default, but rejects it with --strict: "in.C", line 2: error: function "f" cannot be declared inline after its definition at line 1 inline void f(); ^ 1 error detected in the compilation of "in.C".
next prev parent reply other threads:[~2022-08-24 11:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-24 14:12 [Bug c++/66995] New: " anders.granlund.0 at gmail dot com 2015-07-24 15:25 ` [Bug c++/66995] " redi at gcc dot gnu.org 2021-08-27 0:49 ` [Bug c++/66995] [DR317] " pinskia at gcc dot gnu.org 2022-08-24 11:52 ` redi at gcc dot gnu.org 2022-08-24 11:52 ` redi at gcc dot gnu.org 2022-08-24 11:54 ` redi at gcc dot gnu.org [this message] 2022-08-24 12:46 ` whh8b at obs dot cr
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-66995-4-36nlCTz063@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).