From: Paul Jackson <pj@sgi.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: acme@conectiva.com.br, akpm@osdl.org, dag@brattli.net,
jt@hpl.hp.com, linux-kernel@vger.kernel.org,
irda-users@lists.sourceforge.net
Subject: Re: [PATCH] irda: fix type of struct irda_ias_set.attribute.irda_attrib_string.len
Date: Tue, 30 Dec 2003 04:39:01 -0800 [thread overview]
Message-ID: <20031230043901.5e84b214.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311101900120.2881-100000@home.osdl.org>
A couple of months ago, Linus wrote:
> That's why I hate the "sign compare" warning of gcc so much - it warns
> about things that you CANNOT sanely write in any other way. That makes
> that particular warning _evil_, since it encourages people to write crap
> code.
Then get rid of that warning, using -Wno-sign-compare:
The following change to the top level Makefile tells gcc not to complain
about this:
===== Makefile 1.439 vs edited =====
164c164
< HOSTCFLAGS = -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
---
> HOSTCFLAGS = -Wall -Wno-sign-compare -Wstrict-prototypes -O2 -fomit-frame-pointer
278c278
< CFLAGS := -Wall -Wstrict-prototypes -Wno-trigraphs -O2 \
---
> CFLAGS := -Wall -Wno-sign-compare -Wstrict-prototypes -Wno-trigraphs -O2 \
Would you like me to send Andrew a real patch for this?
I have been running all my personal builds with this change for a month
now, ever since I picked up some version of gcc that is fond of that
warning.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2003-12-30 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 2:06 [PATCH] irda: fix type of struct irda_ias_set.attribute.irda_attrib_string.len Arnaldo Carvalho de Melo
2003-11-11 2:59 ` Linus Torvalds
2003-11-11 3:07 ` Linus Torvalds
2003-12-30 12:39 ` Paul Jackson [this message]
2003-11-11 17:18 ` Jean Tourrilhes
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=20031230043901.5e84b214.pj@sgi.com \
--to=pj@sgi.com \
--cc=acme@conectiva.com.br \
--cc=akpm@osdl.org \
--cc=dag@brattli.net \
--cc=irda-users@lists.sourceforge.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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