From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>,
newlib@sourceware.org
Subject: Re: [PATCH] arm: Fix memchr() for Armv8-R
Date: Wed, 9 Dec 2020 12:27:42 +0000 [thread overview]
Message-ID: <e4ac8504-67df-0d83-9d11-a28010df69a5@foss.arm.com> (raw)
In-Reply-To: <ff3d2cd8-ac0b-eec4-a2a3-6fb72e41aa81@embedded-brains.de>
On 09/12/2020 12:11, Sebastian Huber wrote:
> On 04/12/2020 08:42, Sebastian Huber wrote:
>
>> The Cortex-R52 processor is an Armv8-R processor with a NEON unit. This
>> fix prevents conflicting architecture profiles A/R errors issued by the
>> linker.
>>
>> Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
>> ---
>> newlib/libc/machine/arm/memchr.S | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/newlib/libc/machine/arm/memchr.S
>> b/newlib/libc/machine/arm/memchr.S
>> index 7c22b117e..1a4c6512c 100644
>> --- a/newlib/libc/machine/arm/memchr.S
>> +++ b/newlib/libc/machine/arm/memchr.S
>> @@ -79,7 +79,11 @@
>> @ NOTE: This ifdef MUST match the one in memchr-stub.c
>> #if defined (__ARM_NEON__) || defined (__ARM_NEON)
>> +#if __ARM_ARCH >= 8 && __ARM_ARCH_PROFILE == 'R'
>> + .arch armv8-r
>> +#else
>> .arch armv7-a
>> +#endif
>> .fpu neon
>>
>
> The memchr.S from the ARM optimized routines package has little in
> common with the file in Newlib:
>
> https://github.com/ARM-software/optimized-routines/blob/master/string/arm/memchr.S
>
>
> The Newlib variant uses VFP instructions for example.
>
> I think this change should be checked in as is.
>
That probably means the newlib one is out of date and needs to be resynced.
R.
next prev parent reply other threads:[~2020-12-09 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 7:42 Sebastian Huber
2020-12-09 12:11 ` Sebastian Huber
2020-12-09 12:27 ` Richard Earnshaw [this message]
2020-12-09 12:53 ` Sebastian Huber
2020-12-14 21:12 ` Jeff Johnston
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=e4ac8504-67df-0d83-9d11-a28010df69a5@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).