public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: hjl dot tools at gmail dot com <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug c/39026] New: Gcc accepts invalid code
Date: Thu, 29 Jan 2009 20:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0901292000590.25383@digraph.polyomino.org.uk> (raw)
In-Reply-To: <bug-39026-682@http.gcc.gnu.org/bugzilla/>
On Thu, 29 Jan 2009, hjl dot tools at gmail dot com wrote:
> inline void foo ();
>
> int
> main ()
> {
> foo ();
> return 0;
> }
> [hjl@gnu-6 gcc]$ gcc /tmp/i.i -S
If you use -std=c99 -pedantic-errors you get an error, as expected.
You're compiling in gnu89 mode.
If you use -std=c99 without -pedantic-errors you get a duplicate warning:
t.c:1: warning: inline function 'foo' declared but never defined
t.c:1: warning: inline function 'foo' declared but never defined
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-01-29 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 18:31 hjl dot tools at gmail dot com
2009-01-29 18:34 ` [Bug c/39026] " hjl dot tools at gmail dot com
2009-01-29 20:02 ` joseph at codesourcery dot com
2009-01-29 20:09 ` Joseph S. Myers [this message]
2009-01-29 20:09 ` hjl dot tools at gmail dot com
2009-01-29 21:24 ` rguenther at suse dot de
2009-01-30 1:17 ` hjl dot tools at gmail dot com
2009-01-30 6:52 ` rguenther at suse dot de
2009-01-30 16:05 ` hjl dot tools at gmail dot com
2009-01-30 16:44 ` hjl dot tools at gmail dot com
2009-01-31 17:44 ` hjl dot tools at gmail dot com
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=Pine.LNX.4.64.0901292000590.25383@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-bugzilla@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: link
Be 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).