From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: Sandra Loosemore <sandra@codesourcery.com>,
gcc-patches@gcc.gnu.org,
Richard Earnshaw <richard.earnshaw@arm.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
Kyrill Tkachov <kyrylo.tkachov@arm.com>
Subject: Re: Fwd: [PATCH, doc/ARM, ping] Remove false affirmation that Thumb cannot use an FPU
Date: Wed, 17 Aug 2016 10:50:00 -0000 [thread overview]
Message-ID: <a2cc8010-24fe-310d-43b3-7ab86026a84b@foss.arm.com> (raw)
In-Reply-To: <513df5b0-afba-bd3c-b2bb-ef7d67e1023b@foss.arm.com>
Ping?
Best regards,
Thomas
On 11/08/16 11:31, Thomas Preudhomme wrote:
> Hi Sandra,
>
> Thanks for your feedback. Please find an updated version attached to this email.
> ChangeLog entry is unchanged:
>
> *** gcc/ChangeLog ***
>
> 2016-08-02 Thomas Preud'homme <thomas.preudhomme@arm.com>
>
> * doc/fragments.texi (MULTILIB_EXCEPTIONS): Replace example with
> preventing combination of -mfloat-abi=soft with any -mfpu option.
>
> Best regards,
>
> Thomas
>
> On 11/08/16 04:09, Sandra Loosemore wrote:
>> On 08/10/2016 09:51 AM, Thomas Preudhomme wrote:
>>
>>> diff --git a/gcc/doc/fragments.texi b/gcc/doc/fragments.texi
>>> index
>>> b6d8541c8ca820fa732363a05221e2cd4d1251c2..a060635c9cee7374d9d187858ac87acdd08860f2
>>>
>>> 100644
>>> --- a/gcc/doc/fragments.texi
>>> +++ b/gcc/doc/fragments.texi
>>> @@ -117,12 +117,15 @@ specified, there are combinations that should not be
>>> built. In that
>>> case, set @code{MULTILIB_EXCEPTIONS} to be all of the switch exceptions
>>> in shell case syntax that should not be built.
>>>
>>> -For example the ARM processor cannot execute both hardware floating
>>> -point instructions and the reduced size THUMB instructions at the same
>>> -time, so there is no need to build libraries with both of these
>>> -options enabled. Therefore @code{MULTILIB_EXCEPTIONS} is set to:
>>> +For example on ARM targets @code{-mfloat-abi=soft} requests to use a
>>> +softfloat implementation for floating-point operations. Therefore, it
>>
>> For example, on ARM targets @option{-mfloat-abi=soft} requests use of software
>> floating-point operations. Therefore, it
>>
>>> +does not make sense to find both @code{-mfloat-abi=soft} and an
>>
>> @option here too
>>
>>> +@code{mfpu} option on the command line so @code{MULTILIB_EXCEPTIONS}
>>
>> and here @option{-mfpu}
>>
>>> +could contain the following exception (assuming that @code{-mfloat-abi}
>>
>> @option
>>
>>> +comes after in MULTILIB_OPTIONS and given that soft is the default
>>
>> @code markup on MULTILIB_OPTIONS?
>> @samp markup on soft?
>>
>>> +value):
>>> @smallexample
>>> -*mthumb/*mhard-float*
>>> +*mfpu=*
>>> @end smallexample
>>>
>>> @findex MULTILIB_REQUIRED
>>
>> -Sandra
>>
next prev parent reply other threads:[~2016-08-17 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4052511d-541d-9b8b-3000-ba09dc314f7f@foss.arm.com>
2016-08-10 15:51 ` Fwd: [PATCH, doc/ARM] " Thomas Preudhomme
2016-08-11 3:09 ` Sandra Loosemore
2016-08-11 10:31 ` Thomas Preudhomme
2016-08-17 10:50 ` Thomas Preudhomme [this message]
2016-08-18 6:01 ` Sandra Loosemore
2016-08-18 10:05 ` Richard Earnshaw (lists)
2016-08-18 20:00 ` Sandra Loosemore
2016-08-18 10:22 ` Thomas Preudhomme
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=a2cc8010-24fe-310d-43b3-7ab86026a84b@foss.arm.com \
--to=thomas.preudhomme@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=sandra@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).