From: Jeff Garzik <jeff@garzik.org>
To: Satyam Sharma <satyam@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
James Bottomley <james.bottomley@steeleye.com>,
Oliver Neukum <oliver@neukum.name>,
linux-scsi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH -mm] DC395x SCSI driver: Shut up uninitialized variable build warning
Date: Sun, 02 Sep 2007 16:43:28 -0400 [thread overview]
Message-ID: <46DB2070.9010608@garzik.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0709030211040.29617@enigma.security.iitk.ac.in>
Satyam Sharma wrote:
> I'll post the info as a reply to the first mail in this series. I have
> fairly recent gcc (4.1.1) and I don't see us dropping support for it in
> the next few years.
What's important is not support lifetime, but whether or not the warning
persists through version 4.1.2, 4.1.3, etc.
We don't want to add markers for compiler quirks that come and go.
The current markers tend to exist for a class of problems that gcc
fundamentally has a tough time "seeing." Different optimizer behaviors
from compiler version to compiler version are just noise[1].
Jeff
[1] sometimes quite literally, in the case of compiler warnings.
prev parent reply other threads:[~2007-09-02 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.999.0709022344550.27844@enigma.security.iitk.ac.i n>
[not found] ` <alpine.LFD.0.999.0709022344550.27844@enigma.security.iitk.ac.in>
2007-09-02 20:13 ` [PATCH -mm] IPS SCSI driver: Check return of scsi_add_host() Satyam Sharma
2007-09-02 20:03 ` Jesper Juhl
2007-09-02 20:32 ` Jeff Garzik
2007-09-02 22:39 ` Satyam Sharma
2007-09-02 20:23 ` [PATCH -mm] DC395x SCSI driver: Shut up uninitialized variable build warning Satyam Sharma
2007-09-02 20:23 ` Jeff Garzik
2007-09-02 20:49 ` Satyam Sharma
2007-09-02 20:43 ` Jeff Garzik [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=46DB2070.9010608@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oliver@neukum.name \
--cc=satyam@infradead.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 NNTP newsgroup(s).