From: Dan Kegel <dank@kegel.com>
To: wd@denx.de, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: gcc-2.95 broken on PPC?
Date: Thu, 10 Apr 2003 10:52:15 -0700 [thread overview]
Message-ID: <3E95AF4F.20105@kegel.com> (raw)
The Denkster wrote:
>> However, bugs #1 (zlib.c) and #3 (div64.h) disappear if I compile
>> my kernels with gcc-3.2.2 instead of 2.95.4, which is a strong
>> indication that 2.95.4 is broken on PPC. Is this something that's
>
> This is speculation only. We use gcc-2.95.4 as part of our ELDK in
> all of our projects, and a lot of people are using these tools, too.
> We definitely see more problems with gcc-3.x compilers.
Hi Wolfgang, when you say you see more problems with gcc-3.x
compilers, what is x? I'd understand if you saw problems
with gcc-3.0.*, but I had hoped that gcc-3.2.2 would compile
good kernels for ppc.
(Me, I'm still using Montavista Linux 2.0's gcc-2.95.3 to build my ppc kernels,
but am looking for an excuse to switch to gcc-3.2.* or gcc-3.3.*.)
- Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
next reply other threads:[~2003-04-10 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 17:52 Dan Kegel [this message]
2003-04-10 17:50 ` gcc-2.95 broken on PPC? Daniel Jacobowitz
2003-04-10 21:20 ` Wolfgang Denk
2003-04-10 21:32 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2003-04-12 15:36 Dan Kegel
2003-04-12 19:12 ` Peter Barada
2003-04-11 15:01 mikpe
2003-04-10 12:56 mikpe
2003-04-10 14:20 ` Benjamin Herrenschmidt
2003-04-10 14:42 ` Wolfgang Denk
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=3E95AF4F.20105@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wd@denx.de \
/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