From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
Bernd Eckenfels <ecki-lkm@lina.inka.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make gcc3.3 Eliminate Unused Static Functions
Date: Thu, 19 Jun 2003 15:28:10 +0200 [thread overview]
Message-ID: <20030619132810.GA6906@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030613160335.GO828@ip68-0-152-218.tc.ph.cox.net>
On Fri, 13 June 2003 09:03:35 -0700, Tom Rini wrote:
>
> ... only if we say a min gcc version of 3.3 however, yes? Otherwise the
> kernel gets rather bloated. Just how wide-spread (and Good To Use) is
> gcc-3.3 now?
I haven't seen a clear compiler bug yet, but found two bugs in
assembler code with 2.95.3 that compiled without problems with 3.2.x.
One of them has actually hit people, as you could see in the code.
Most symptoms were "fixed", but the cause remained.
If nothing else, I'd like to keep 2.95 as a code checker for at least
a year or two. Give 3.x some more time to mature.
Jörn
--
Measure. Don't tune for speed until you've measured, and even then
don't unless one part of the code overwhelms the rest.
-- Rob Pike
next prev parent reply other threads:[~2003-06-19 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 0:17 Rusty Russell
2003-06-13 3:01 ` Bernd Eckenfels
2003-06-13 14:04 ` Chris Friesen
2003-06-13 16:03 ` Tom Rini
2003-06-13 18:07 ` Robert Love
2003-06-13 18:15 ` Tom Rini
2003-06-13 18:41 ` Robert Love
2003-06-19 12:10 ` Adrian Bunk
2003-06-19 13:28 ` Jörn Engel [this message]
2003-06-19 13:57 ` Bob Tracy
2003-06-19 14:32 ` Chris Meadors
2003-06-13 1:03 Rusty Russell
2003-06-19 12:17 ` Adrian Bunk
2003-06-20 2:28 ` Rusty Russell
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=20030619132810.GA6906@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=cfriesen@nortelnetworks.com \
--cc=ecki-lkm@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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
all inboxes | Powered by JetHome®