public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brendan J Simon <brendan.simon@bigpond.com>
To: Tim Bowman <tbowman@emware.com>
Cc: mtd mailing list <mtd@infradead.org>
Subject: Re: RPX Classic/Lite and byte ordering
Date: Tue, 03 Apr 2001 11:16:11 +1000	[thread overview]
Message-ID: <3AC9245B.4000205@bigpond.com> (raw)
In-Reply-To: 3AC8E6A2.E0E43DC1@emware.com

Nope.  A powerpc cross compiler *should* produce *exactly* the same code 
as a naitive compiler.  This assumes you are using exactly the same 
version of gcc, gas and glibc.  Having said that, I just remembered that 
the PowerPC architecture can be big endian or little endian.  There must 
be a configuration option when building the compilers that sets the 
default.  You should be able to specify which you want, either in the 
spec file or on the command line.

I've had a look at my spec file.  Try the -mbig-endian (or -mbig) for 
big endian.  Try -mlittle-endian (or -mlittle) for little endian.  I 
prefer -mbig-endian or -mlittle-endian because they are a lot clearer 
than -mbig or -mlittle.

My spec file has the following:

*multilib_defaults:
mbig mcall-linux

*cpp_endian_default:
%(cpp_endian_big)

*cc1_endian_default:
%(cc1_endian_big_spec)


Regards,
Brendan Simon.



Tim Bowman wrote:

> Would cross-compiling the kernel on an x86 produce different ordering
> than compiling natively on a PowerPC (which is how I am building it)? 
> Maybe I need to build it on an x86?





To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-04-03  0:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 20:52 RPX Classic/Lite and byte ordering Tim Bowman
2001-04-03  1:16 ` Brendan J Simon [this message]
2001-04-03  0:42   ` mferrell
  -- strict thread matches above, loose matches on Subject: below --
2001-04-02 20:40 Tim Bowman
2001-03-30 17:43 Tim Bowman

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=3AC9245B.4000205@bigpond.com \
    --to=brendan.simon@bigpond.com \
    --cc=mtd@infradead.org \
    --cc=tbowman@emware.com \
    /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