From: Ian Lance Taylor <ian@wasabisystems.com>
To: Pierre Habraken <Pierre.Habraken@imag.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Arm and big endian
Date: Tue, 18 May 2004 15:09:00 -0000 [thread overview]
Message-ID: <m3iset22vc.fsf@gossamer.airs.com> (raw)
In-Reply-To: <40AA1A03.C24308D8@imag.fr>
Pierre Habraken <Pierre.Habraken@imag.fr> writes:
> I want to compile gcc and newlib so that big endian code is generated
> for newlib (this is for teaching purpose).
>
> Though I understand that multilib is activated by default, I do not need
> the multilib option since I want 32 bits and big endian code only.
>
> The configure doc. (in INSTALL dir.) says that there is an option for
> disabling biendian (BTW, does here "bi" mean "big" or "bi-" ?...), but
> nothing for enabling it.
>
> I tried --enable-biendian : configure does not complain about it but
> apparently does not take it in account.
>
> So my question is : What configure option I have to set up for gcc in
> order to get newlib being cross-compiled to big endian code ?
>
> Has someone succeeded in doing that (with or without multilib support) ?
I don't think there is any way to do that without patching the source.
It's easy to patch the source to make -mbig-endian the default: change
the definition of TARGET_DEFAULT to include ARM_FLAG_BIG_END.
TARGET_DEFAULT is defined in config/arm/*.h; the exact definition
depends upon your target.
It is only slightly more work to add support for --with-endian to
config.gcc.
Ian
next prev parent reply other threads:[~2004-05-18 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 14:11 Pierre Habraken
2004-05-18 15:09 ` Ian Lance Taylor [this message]
2004-05-24 12:20 ` Pierre Habraken
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=m3iset22vc.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=Pierre.Habraken@imag.fr \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).