From: Robert Love <rml@tech9.net>
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: 13 Jun 2003 18:41:56 +0000 [thread overview]
Message-ID: <1055529716.1123.1.camel@localhost> (raw)
In-Reply-To: <20030613181516.GT828@ip68-0-152-218.tc.ph.cox.net>
On Fri, 2003-06-13 at 18:15, Tom Rini wrote:
> But how much have you rebuilt, heavily tested, etc? I know that
> currently Debian/sid is building XFree86 4.1 at -O on all arches due to
> gcc-3.3 issues (some xdm auth problem on ppc and x86, other things
> elsewhere).
I believe Red Hat Rawhide (what I am running) is built with gcc 3.3.
Anyhow, my point was we _don't_ know if its ready so we cannot start
doing things which are detrimental to users of earlier kernels. I was
just adding that it does seem to compile the kernel fine for me, at
least.
Robert Love
next prev parent reply other threads:[~2003-06-13 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 0:17 [PATCH] Make gcc3.3 Eliminate Unused Static Functions 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 [this message]
2003-06-19 12:10 ` Adrian Bunk
2003-06-19 13:28 ` Jörn Engel
2003-06-19 13:57 ` Bob Tracy
2003-06-19 14:32 ` Chris Meadors
-- strict thread matches above, loose matches on Subject: below --
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=1055529716.1123.1.camel@localhost \
--to=rml@tech9.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.