From: Richard Henderson <rth@twiddle.net>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: richbaum@acm.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] More compile warning fixes for 2.4.0
Date: Mon, 8 Jan 2001 21:30:44 -0800 [thread overview]
Message-ID: <20010108213044.A28968@twiddle.net> (raw)
In-Reply-To: <3A5790E3.18256.963C79@localhost> <20010108205001.S3472@arthur.ubicom.tudelft.nl>
In-Reply-To: <20010108205001.S3472@arthur.ubicom.tudelft.nl>
On Mon, Jan 08, 2001 at 08:50:01PM +0100, Erik Mouw wrote:
> Is this really a kernel bug? This is common idiom in C, so gcc
> shouldn't warn about it. If it does, it is a bug in gcc IMHO.
No, it is not a common idiom in C. It has _never_ been valid C.
GCC originally allowed it due to a mistake in the grammar; we
now warn for it. Fix your source.
r~
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 5:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 2:40 [PATCH] More compile warning fixes for 2.4.0 Rich Baum
2001-01-07 12:41 ` Paul Gortmaker
2001-01-07 13:17 ` Keith Owens
2001-01-08 19:50 ` Erik Mouw
2001-01-08 20:17 ` Alan Cox
2001-01-09 5:30 ` Richard Henderson [this message]
2001-01-09 10:02 ` Albert D. Cahalan
2001-01-09 15:10 ` Richard B. Johnson
2001-01-09 18:51 ` Linus Torvalds
2001-01-09 21:24 ` Albert D. Cahalan
2001-01-09 21:31 ` Linus Torvalds
2001-01-10 2:20 ` Andrea Arcangeli
2001-01-10 7:10 ` Linus Torvalds
2001-01-10 13:17 ` Rich Baum
2001-01-10 13:32 ` Andrea Arcangeli
2001-01-10 16:03 ` Marco Colombo
2001-01-10 16:52 ` Alan Shutko
2001-01-10 17:32 ` Marco Colombo
2001-01-10 17:19 ` Linus Torvalds
2001-01-10 18:02 ` Marco Colombo
2001-01-10 1:58 ` Rich Baum
2001-01-09 1:23 ` Rich Baum
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=20010108213044.A28968@twiddle.net \
--to=rth@twiddle.net \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=richbaum@acm.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.