public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
Cc: Jeffrey Hammel <jhammel@EECS.Berkeley.EDU>,
gcc-bugs@gcc.gnu.org, alanwu@langmuir.eecs.berkeley.edu
Subject: Re: gcc "bug"
Date: Tue, 17 Feb 2004 00:49:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0402170045410.8953@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87y8r21ykf.fsf@student.uni-tuebingen.de>
On Mon, 16 Feb 2004, Falk Hueffner wrote:
> You need -Wimplicit (or -Wall) to get a warning. This is by design,
> since many old sources use implicit declarations. For new source, you
> should always use -Wall.
Note that these warnings are on by default (and can't be turned off with
-Wno-implicit - mandatory pedwarns) in C99 mode as implicit declarations
are not part of the C99 language at all, so if and when C99 is fully
implemented and -std=gnu99 becomes the default, these warnings will also
be on by default.
--
Joseph S. Myers
jsm@polyomino.org.uk
next prev parent reply other threads:[~2004-02-17 0:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 21:39 Jeffrey Hammel
2004-02-16 21:53 ` Falk Hueffner
2004-02-17 0:49 ` Joseph S. Myers [this message]
[not found] <8F542C9341D3D211BC880008C75DFE100530BCB2@rba.gov.au>
2000-11-12 17:22 ` gcc bug ? Phil Edwards
[not found] <393BC0AD.DC25507B@rtp.ericsson.com>
[not found] ` <14651.56471.760657.974882@rtp.ericsson.se>
2000-06-05 12:43 ` gcc bug? Martin v. Loewis
-- strict thread matches above, loose matches on Subject: below --
2000-02-14 8:06 GCC bug! Fabio Alemagna
1999-10-31 23:03 gcc bug? Bill Mills-Curran
1999-10-20 11:41 Mike Stump
1999-09-30 19:57 Joao Belo
1999-09-30 19:57 ` Martin v. Loewis
1999-06-30 23:07 Chris Cochrane
1999-06-15 2:14 ` Franz Sirl
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.58.0402170045410.8953@digraph.polyomino.org.uk \
--to=jsm@polyomino.org.uk \
--cc=alanwu@langmuir.eecs.berkeley.edu \
--cc=falk.hueffner@student.uni-tuebingen.de \
--cc=gcc-bugs@gcc.gnu.org \
--cc=jhammel@EECS.Berkeley.EDU \
/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).