From: Wolfgang Denk <wd@denx.de>
To: mikpe@csd.uu.se
Cc: linuxppc-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: Re: gcc-2.95 broken on PPC?
Date: Thu, 10 Apr 2003 16:42:46 +0200 [thread overview]
Message-ID: <20030410144251.9B83CC5877@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 10 Apr 2003 14:56:28 +0200." <200304101256.h3ACuSw3022796@harpo.it.uu.se>
In message <200304101256.h3ACuSw3022796@harpo.it.uu.se> you wrote:
>
> It seems gcc-2.95, specifically 2.95.4 as included in YDL2.3,
> generates incorrect code for recent 2.4 standard kernels on PPC.
Ummm.. do you have any direct evidence, i. e. a source file where the
generated object code is obviously wrong?
> 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.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Overflow on /dev/null, please empty the bit bucket.
next prev parent reply other threads:[~2003-04-10 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 12:56 mikpe
2003-04-10 14:20 ` Benjamin Herrenschmidt
2003-04-10 14:42 ` Wolfgang Denk [this message]
2003-04-10 17:52 Dan Kegel
2003-04-10 17:50 ` Daniel Jacobowitz
2003-04-10 21:20 ` Wolfgang Denk
2003-04-10 21:32 ` Jörn Engel
2003-04-11 15:01 mikpe
2003-04-12 15:36 Dan Kegel
2003-04-12 19:12 ` Peter Barada
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=20030410144251.9B83CC5877@atlas.denx.de \
--to=wd@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mikpe@csd.uu.se \
/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®