From: Michael Ellerman <michael@ellerman.id.au>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: kexec@lists.infradead.org, cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] kexec trouble with gcc-4.3
Date: Fri, 03 Apr 2009 13:47:44 +1100 [thread overview]
Message-ID: <1238726864.6802.11.camel@localhost> (raw)
In-Reply-To: <49D56FB1.4070605@am.sony.com>
[-- Attachment #1.1: Type: text/plain, Size: 958 bytes --]
On Thu, 2009-04-02 at 19:08 -0700, Geoff Levand wrote:
> On 04/02/2009 05:04 PM, Michael Ellerman wrote:
> > On Thu, 2009-04-02 at 11:40 -0700, Geoff Levand wrote:
> >> Hi,
> >>
> >> I tried building kexec with gcc-4.3 from the cell sdk-3.1
> >> and the resulting binary didn't work correctly. It works
> >> OK with the gcc-4.1 from the same (sdk-3.1).
> >
> > You mean building kexec-tools? Or building the kernel?
>
> The kexec program in kexec-tools.
Right. In that case I'd guess there's a bug in the kexec-tools DT
creation code, that's being exposed by the new gcc.
If you compare the DT from a working and non-working version it
shouldn't be too hard to track down.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-04-03 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 18:40 kexec trouble with gcc-4.3 Geoff Levand
2009-04-03 0:04 ` [Cbe-oss-dev] " Michael Ellerman
2009-04-03 2:08 ` Geoff Levand
2009-04-03 2:47 ` Michael Ellerman [this message]
2009-06-22 22:08 ` Geoff Levand
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=1238726864.6802.11.camel@localhost \
--to=michael@ellerman.id.au \
--cc=cbe-oss-dev@ozlabs.org \
--cc=geoffrey.levand@am.sony.com \
--cc=kexec@lists.infradead.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