linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Don't use HOSTCFLAGS in BOOTCFLAGS
Date: Tue, 29 May 2007 09:21:30 -0500	[thread overview]
Message-ID: <1180448490.3360.52.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <20070529053712.GE30266@localhost.localdomain>

On Tue, 2007-05-29 at 15:37 +1000, David Gibson wrote:
> In the bootwrapper code for powerpc, we include HOSTCFLAGS into the
> BOOTCFLAGS used for buildinf the zImage wrapper code.  Since the
> wrapper code is not host code, this makes no sense.  This patch
> removes the use of HOSTCFLAGS here, instead including directly into
> BOOTCFLAGS those flags from the normal kernel CFLAGS which also make
> sense in the bootwrapper code.
> 
> In particular, this makes the bootwrapper use -msoft-float, preventing
> the compiler from generating floating point instructions.  Previously,
> under some circumstances the compiler could generate floating point
> instructions in the bootwrapper which would cause exceptions on
> embedded CPUS which don't have floating point support.

This is essentially the cleanup Paul asked me to do of my original
-msoft-float addition.  Matches the patch I have sitting locally that I
haven't gotten around to sending out yet.

> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Acked-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>

  reply	other threads:[~2007-05-29 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  5:37 Don't use HOSTCFLAGS in BOOTCFLAGS David Gibson
2007-05-29 14:21 ` Josh Boyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-29  3:29 David Gibson
2007-05-29  5:12 ` Segher Boessenkool
2007-05-29  5:34   ` David Gibson
2007-05-29  6:26     ` Segher Boessenkool
2007-05-29  6:33       ` David Gibson

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=1180448490.3360.52.camel@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).