From: "Rich Baum" <baumr1@coral.indstate.edu>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>, linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] More compile warning fixes for 2.4.0
Date: Mon, 8 Jan 2001 20:23:56 -0500 [thread overview]
Message-ID: <3A5A21DC.11296.5CFA3C@localhost> (raw)
In-Reply-To: <20010108205001.S3472@arthur.ubicom.tudelft.nl>
In-Reply-To: <3A5790E3.18256.963C79@localhost>; from baumr1@coral.indstate.edu on Sat, Jan 06, 2001 at 09:40:51PM -0500
On 8 Jan 2001, at 20:50, Erik Mouw wrote:
> On Sat, Jan 06, 2001 at 09:40:51PM -0500, Rich Baum wrote:
> > Here's a patch that fixes more of the compile warnings with gcc
> > 2.97.
>
> > - case FORE200E_STATE_BLANK:
> > + case FORE200E_STATE_BLANK:;
>
> 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.
>
>
> Erik
> (compiling a GCC CVS snapshot to see if it really breaks)
>
> --
> J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
> of Electrical Engineering, Faculty of Information Technology and Systems,
> Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
> Phone: +31-15-2783635 Fax: +31-15-2781843 Email: J.A.K.Mouw@its.tudelft.nl
> WWW: http://www-ict.its.tudelft.nl/~erik/
> -
> 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/
It still compiles and works just as well as it does without the patch.
Without the patch it says:
warning: deprecated use of label at end of compound statement
My patches are basically telling the compiler to be quiet. If you
use egcs it won't give these warnings even if the code hasn't been
patched.
-
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/
prev parent reply other threads:[~2001-01-09 1:26 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
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 [this message]
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=3A5A21DC.11296.5CFA3C@localhost \
--to=baumr1@coral.indstate.edu \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=linux-kernel@vger.kernel.org \
--cc=richbaum@acm.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