From: Paul Brook <paul@codesourcery.com>
To: gcc@gcc.gnu.org
Cc: Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: arm-elf multilib issues
Date: Thu, 01 Oct 2009 14:19:00 -0000 [thread overview]
Message-ID: <200910011519.10575.paul@codesourcery.com> (raw)
In-Reply-To: <4AC4AF2E.50704@oarcorp.com>
> Do we want to enable more multilibs in arm-elf?
Almost certainly not. As far as I'm concerned arm-elf is obsolete, and in
maintenance only mode. You should be using arm-eabi.
IMHO building lots of multilibs by default significantly increases toolchain
size and build time for little actual benefit. ARM CPUs are generally
backwards compatible and we only have one important ABI variant, so very few
multilibs are required for a functional toolchain. Anybody who cares about
optimized runtime libraries probably wants tuning for their exact setup,
rather than whatever arbitrary selections you're going to choose.
Paul
next prev parent reply other threads:[~2009-10-01 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 13:31 Joel Sherrill
2009-10-01 14:19 ` Paul Brook [this message]
2009-10-01 20:35 ` Joel Sherrill
2009-10-01 23:10 ` Paul Brook
2009-10-01 22:48 ` zoltan
2009-10-01 23:22 ` Paul Brook
2009-10-02 1:00 ` Alexandre Pereira Nunes
2009-10-02 1:12 ` zoltan
2009-10-02 19:24 ` Samuel Tardieu
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=200910011519.10575.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=joel.sherrill@oarcorp.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).