From: Samuel Tardieu <sam@rfc1149.net>
To: Paul Brook <paul@codesourcery.com>
Cc: gcc@gcc.gnu.org, Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: arm-elf multilib issues
Date: Fri, 02 Oct 2009 19:24:00 -0000 [thread overview]
Message-ID: <2009-10-02-21-23-45+trackit+sam@rfc1149.net> (raw)
In-Reply-To: <200910011519.10575.paul@codesourcery.com> (Paul Brook's message of "Thu, 1 Oct 2009 15:19:10 +0100")
>>>>> "Paul" == Paul Brook <paul@codesourcery.com> writes:
Paul> IMHO building lots of multilibs by default significantly increases
Paul> toolchain size and build time for little actual benefit. ARM CPUs
Paul> are generally backwards compatible and we only have one important
Paul> ABI variant, so very few multilibs are required for a functional
Paul> toolchain.
I have had problem in the past with Cortex M3 based processors because
libraries were not compiled with the Thumb-2 instruction set (which is
the only one supported by those ARM CPUs) variant.
Sam
--
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/
prev parent reply other threads:[~2009-10-02 19:24 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
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 [this message]
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=2009-10-02-21-23-45+trackit+sam@rfc1149.net \
--to=sam@rfc1149.net \
--cc=gcc@gcc.gnu.org \
--cc=joel.sherrill@oarcorp.com \
--cc=paul@codesourcery.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).