public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@cygnus.com>
To: Nick Clifton <nickc@cygnus.com>
Cc: naeem.m.afzal@intel.com, gcc@gcc.gnu.org
Subject: Re: gcc for big-endian as default
Date: Wed, 02 Aug 2000 13:52:00 -0000	[thread overview]
Message-ID: <20000802165255.49914@cse.cygnus.com> (raw)
In-Reply-To: <200008022034.NAA15802@elmo.cygnus.com>

On Wed, Aug 02, 2000 at 01:34:45PM -0700, Nick Clifton wrote:
> Hi Naeem,
> 
> : > How could I make gcc crosscompiler (ARM-LINUX) to compile with
> : > target paltform as big-endian, so that when compiling with this
> : > compiler, I dont have to use -mbig-endian every time.
> 
> The simplest method is to add the -mbig-endian switch to CC1_SPEC
> defiend in gcc/config/arm/arm.h, like this:
> 
>   #define CC1_SPEC "-mbig-endian"
> 
> Note, that you will probably also want to change the defintion of
> CPP_ENDIAN_DEFAULT_SPEC to reflect this change.
> 
> Also you ought to change the defintion of MULTILIB_DEFAULTS in
> gcc/config/arm/linux-elf.h again to reflect this change.

The ARM maintainers might want to think about providing support directly.
Looking at config.sub, it looks like armbe-* and armle-* specifically select
between big and little endian defaults.  I did a similar thing with the Powerpc
-- configuring powerpc-eabi selects the big endian as default, and configuring
powerpcle-eabi selects the little endian as default.

-- 
Michael Meissner, Red Hat, Inc.
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work:	  meissner@redhat.com		phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org	fax:   +1 978-692-4482

  reply	other threads:[~2000-08-02 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-02 13:34 Nick Clifton
2000-08-02 13:52 ` Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-01 18:43 Afzal, Naeem M
2000-08-02 12:44 ` Erik Mouw

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=20000802165255.49914@cse.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=naeem.m.afzal@intel.com \
    --cc=nickc@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).