mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Dan Kegel <dank@kegel.com>
Cc: 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 23:32:32 +0200	[thread overview]
Message-ID: <20030410213232.GB31167@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <3E95AF4F.20105@kegel.com>

On Thu, 10 April 2003 10:52:15 -0700, Dan Kegel wrote:
> 
> 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.*.)

We've had a "problem" with 3.2. Some conditional new code looked like
this:

#define LONG_MACRO \
	asm \
	asm \
	asm \
#ifdef FOO \
	asm \
	asm \
#else \
	asm \
#endif \
	asm \
	asm

Interesting, isn't it? The fun part was that it was compiling cleanly
in 3.2, but not in 2.95.
Sadly, noone bothered to compile this with 2.95 for a long time.

Jörn

-- 
More computing sins are committed in the name of efficiency (without
necessarily achieving it) than for any other single reason - including
blind stupidity.
-- W. A. Wulf 

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- 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=20030410213232.GB31167@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=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

all inboxes | Powered by JetHome®