From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>,
Prakhar Bahuguna <prakhar.bahuguna@arm.com>,
gcc-patches@gcc.gnu.org
Cc: Richard.Earnshaw@arm.com, Ramana.Radhakrishnan@arm.com
Subject: Re: [PATCH, GCC/ARM, Stage 1] Rename FPSCR builtins to correct names
Date: Fri, 23 Jun 2017 15:54:00 -0000 [thread overview]
Message-ID: <594D399B.8030104@foss.arm.com> (raw)
In-Reply-To: <9982d9c9-ee19-c423-1e47-d0993987d369@foss.arm.com>
Hi Thomas,
On 23/06/17 16:48, Thomas Preudhomme wrote:
> Hi Kyrill,
>
> On 10/04/17 15:01, Kyrill Tkachov wrote:
>> Hi Prakhar,
>> Sorry for the delay,
>>
>> On 22/03/17 10:46, Prakhar Bahuguna wrote:
>>> The GCC documentation in section 6.60.8 ARM Floating Point Status and Control
>>> Intrinsics states that the FPSCR register can be read and written to using the
>>> intrinsics __builtin_arm_get_fpscr and __builtin_arm_set_fpscr. However, these
>>> are misnamed within GCC itself and these intrinsic names are not recognised.
>>> This patch corrects the intrinsic names to match the documentation, and adds
>>> tests to verify these intrinsics generate the correct instructions.
>>>
>>> Testing done: Ran regression tests on arm-none-eabi for Cortex-M4.
>>>
>>> 2017-03-09 Prakhar Bahuguna <prakhar.bahuguna@arm.com>
>>>
>>> gcc/ChangeLog:
>>>
>>> * gcc/config/arm/arm-builtins.c (arm_init_builtins): Rename
>>> __builtin_arm_ldfscr to __builtin_arm_get_fpscr, and rename
>>> __builtin_arm_stfscr to __builtin_arm_set_fpscr.
>>> * gcc/testsuite/gcc.target/arm/fpscr.c: New file.
>>>
>>> Okay for stage 1?
>>
>> I see that the mistake was in not addressing one of the review comments in:
>> https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01832.html
>> properly in the patch that added these functions :(
>>
>> This is ok for stage 1 if a bootstrap and test on arm-none-linux-gnueabihf works
>> fine
>> I don't think we want to maintain the __builtin_arm_[ld,st]fscr names for
>> backwards compatibility
>> as they were not documented and are __builtin_arm* functions that we don't
>> guarantee to maintain.
>
> How about a backport to GCC 5, 6 & 7? The patch applied cleanly on each of these versions and the testsuite didn't show any regression for any of the backport when run for Cortex-M7.
Yes, thanks.
These were always documented "correctly". The patch makes sure the implementation matches that documentation.
Kyrill
>
> Patches attached for reference.
>
> ChangeLog entries:
>
> *** gcc/ChangeLog ***
>
> 2017-06-20 Thomas Preud'homme <thomas.preudhomme@arm.com>
>
> Backport from mainline
> 2017-05-04 Prakhar Bahuguna <prakhar.bahuguna@arm.com>
>
> * gcc/config/arm/arm-builtins.c (arm_init_builtins): Rename
> __builtin_arm_ldfscr to __builtin_arm_get_fpscr, and rename
> __builtin_arm_stfscr to __builtin_arm_set_fpscr.
>
>
> *** gcc/testsuite/ChangeLog ***
>
> 2017-06-20 Thomas Preud'homme <thomas.preudhomme@arm.com>
>
> Backport from mainline
> 2017-05-04 Prakhar Bahuguna <prakhar.bahuguna@arm.com>
>
> gcc/testsuite/
> * gcc.target/arm/fpscr.c: New file.
>
>
> Best regards,
>
> Thomas
next prev parent reply other threads:[~2017-06-23 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 10:46 Prakhar Bahuguna
2017-04-10 12:26 ` Prakhar Bahuguna
2017-04-10 14:01 ` Kyrill Tkachov
2017-06-20 13:49 ` [arm-embedded] " Thomas Preudhomme
2017-06-23 15:49 ` Thomas Preudhomme
2017-06-23 15:54 ` Kyrill Tkachov [this message]
2017-06-23 19:10 ` Christophe Lyon
2017-06-26 11:20 ` 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=594D399B.8030104@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=prakhar.bahuguna@arm.com \
--cc=thomas.preudhomme@foss.arm.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).