From: Linus Torvalds <torvalds@linux-foundation.org>
To: Josh Triplett <josh@freedesktop.org>
Cc: linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@ftp.linux.org.uk>
Subject: Re: sparse -Wptr-subtraction-blows: still needed?
Date: Tue, 1 May 2007 14:43:30 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705011442320.3808@woody.linux-foundation.org> (raw)
In-Reply-To: <4637AC3D.6000008@freedesktop.org>
On Tue, 1 May 2007, Josh Triplett wrote:
>
> Does this still apply? Do current versions of GCC still have this problem?
> If not, can the option and warning go away?
Even if current versions of gcc don't triple the build time (and for the
kernel, I suspect it doesn't, because we've tried to clean up our header
files), the generated _code_ will invariably suck.
So I'd not want to remove the warning.
Linus
next prev parent reply other threads:[~2007-05-01 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 21:08 Josh Triplett
2007-05-01 21:43 ` Linus Torvalds [this message]
2007-05-01 23:59 ` Josh Triplett
2007-05-02 0:24 ` Linus Torvalds
2007-05-02 0:35 ` Al Viro
2007-05-02 12:02 ` Alan Cox
2007-05-02 13:19 ` Andi Kleen
2007-05-02 0:26 ` Al Viro
2007-05-02 0:02 ` Al Viro
2007-05-02 2:42 ` Dave Jones
2007-05-02 13:03 ` Andi Kleen
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=alpine.LFD.0.98.0705011442320.3808@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®