linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Dan Kegel <dank@kegel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: gcc-2.95 broken on PPC?
Date: Thu, 10 Apr 2003 23:20:50 +0200	[thread overview]
Message-ID: <20030410212055.B6A18C5877@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 10 Apr 2003 10:52:15 PDT." <3E95AF4F.20105@kegel.com>

In message <3E95AF4F.20105@kegel.com> you wrote:
> The Denkster wrote:
>
> > 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

There were serios problems with 3.0. I never tested 3.1.  I  believed
3.2  was OK, but I every now and then problems pop up that seem to be
compiler related. Never found time to investigate, though.

> 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.*.)

I just heard that gdb 5.2.1 shows some problems when built  with  gcc
3.2  as  sipped with RH-8.0, and the problem goes away when compiling
with 2.95.[34]. The information might be wrong  or  a  misinterpreta-
tion, but I'm still suspicious.

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
Why is an average signature file longer than an average Perl script??

  parent reply	other threads:[~2003-04-10 21:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 17:52 gcc-2.95 broken on PPC? Dan Kegel
2003-04-10 17:50 ` Daniel Jacobowitz
2003-04-10 21:20 ` Wolfgang Denk [this message]
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=20030410212055.B6A18C5877@atlas.denx.de \
    --to=wd@denx.de \
    --cc=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).