From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [arm-embedded] [embedded-7-branch] Remove ARMv7E-M FPV4-SP-D16 build from rmprofile multilib
Date: Mon, 10 Jul 2017 14:59:00 -0000 [thread overview]
Message-ID: <c2dd01be-2d36-8734-58e8-d257ebd32d89@foss.arm.com> (raw)
In-Reply-To: <8ee4d3d3-b3d7-8348-9faa-a953d177fb4b@foss.arm.com>
Likewise for embedded-7-branch.
Best regards,
Thomas
On 10/07/17 15:16, Thomas Preudhomme wrote:
> Hi,
>
> The new instructions in FPV5-SP-D16 compared to FPv4-SP-D16 are not
> generated when building libgcc, newlib of libstdc++ such that libgcc.a,
> libc.a and libstdc++.a have the same objdump output for these two
> variants. It is therefore a waste of build time to be building a
> multilib for ARMv7E-M FPV5-SP-D16 when selecting rmprofile multilib
> variant. This patch applied to embedded-6-branch removes that multilib
> and map FPv5-SP-D16 to FPv4-SP-D16.
>
> ChangeLog entry is as follows:
>
> *** gcc/ChangeLog.arm ***
>
> 2017-07-04 Thomas Preud'homme <thomas.preudhomme@arm.com>
>
> * config/arm/t-rmprofile: Remove multilibs for fpv5-sp-d16 and map it to
> fpv4-sp-d16.
>
> Tested by configuring GCC with --with-multilib-list=rmprofile, building it and
> running the following:
>
> % ./install/bin/arm-none-eabi-gcc -march=armv7e-m -mfpu=fpv5-sp-d16
> -mfloat-abi=hard -print-multi-directory
> thumb/v7e-m/fpv4-sp/hard
>
> % ./install/bin/arm-none-eabi-gcc -march=armv7e-m -mfpu=fpv5-sp-d16
> -mfloat-abi=softfp -print-multi-directory
> thumb/v7e-m/fpv4-sp/softfp
>
> Best regards,
>
> Thomas
prev parent reply other threads:[~2017-07-10 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 14:16 [arm-embedded] [embedded-6-branch] " Thomas Preudhomme
2017-07-10 14:59 ` Thomas Preudhomme [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=c2dd01be-2d36-8734-58e8-d257ebd32d89@foss.arm.com \
--to=thomas.preudhomme@foss.arm.com \
--cc=gcc-patches@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).