From: Segher Boessenkool <segher@kernel.crashing.org>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: gcc-4.2.0 breakage on powerpc?
Date: Sat, 19 May 2007 18:13:16 +0200 [thread overview]
Message-ID: <c394a611c69fb750d458c089be118e8b@kernel.crashing.org> (raw)
In-Reply-To: <464F167A.1090706@anagramm.de>
> Over here, the 2.6.21.1 Kernel _builds_ fine with gcc-4.2.0 on an
> mpc8540 e500 powerpc
> (mpc8540_ads_defconfig)
Yeah, this problem likely doesn't show up on 32-bit platforms.
> but it just crashes silently on boot. But that's IMHO a
> DeviceTree/U-Boot issue I haven't solved yet.
Quite possible. If you have any further problems, take
it to the linuxppc-dev list please.
Segher
next prev parent reply other threads:[~2007-05-19 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 9:53 gcc-4.2.0 breakage on powerpc? Mikael Pettersson
2007-05-19 12:51 ` Segher Boessenkool
2007-05-19 16:11 ` Segher Boessenkool
2007-05-19 15:23 ` Clemens Koller
2007-05-19 16:13 ` Segher Boessenkool [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-19 17:28 Mikael Pettersson
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=c394a611c69fb750d458c089be118e8b@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=clemens.koller@anagramm.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.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