public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66995] New: First declaration as inline after definition of function Date: Fri, 24 Jul 2015 14:12:00 -0000 [thread overview] Message-ID: <bug-66995-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66995 Bug ID: 66995 Summary: First declaration as inline after definition of function Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: anders.granlund.0 at gmail dot com Target Milestone: --- Consider the following program (prog.cc): void f() {} inline void f(); int main() {} It is ill-formed by [dcl.fct.spec]/4 (http://eel.is/c++draft/dcl.fct.spec#4): "If the definition of a function appears in a translation unit before its first declaration as inline, the program is ill-formed." Therefore I expected gcc to give at least one diagnostic message when compiling it, but I get none with the following command line: g++ prog.cc -std=c++98 -pedantic-errors I have tried with gcc HEAD 6.0.0 20150722 here: http://melpon.org/wandbox/permlink/c6wrML22huCFZMxp
next reply other threads:[~2015-07-24 14:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-24 14:12 anders.granlund.0 at gmail dot com [this message] 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 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@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).