From: Stefan Roese <sr@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, sjg@chromium.org,
Wolfgang Denk <wd@denx.de>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: Re: [PATCH v6 3/3] arm64: Kconfig: Enable usage of optimized memset/memcpy/memmove
Date: Fri, 24 Sep 2021 09:21:54 +0200 [thread overview]
Message-ID: <f34ea18c-d636-fac8-0570-291c874236e1@denx.de> (raw)
In-Reply-To: <20210923195615.GA19126@bill-the-cat>
Hi Tom,
On 23.09.21 21:56, Tom Rini wrote:
> On Thu, Sep 02, 2021 at 05:00:19PM +0200, Stefan Roese wrote:
>
>> This patch enables the use of the optimized memset(), memmove() &
>> memcpy() versions recently added on ARM64.
>>
>> Please note that these optimized functions are now only enabled for
>> recent GCC versions (>= 9.4), as earlier GCC versions throw these
>> errors:
>>
>> aarch64-linux-ar: warning: arch/arm/lib/memset-arm64.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
>> ...
>>
>> Signed-off-by: Stefan Roese <sr@denx.de>
>
> So, I'm tempted to re-do this patch with default off, on ARM64. As-is,
> this causes failure to boot on two similar but different TI platforms
> (am65x_evm_a53, j721e_evm_a72) and my amlogic Le Potato (libretech-cc).
> This seems to be fine on my Pi 3.
If this generates problems on some ARM64 platforms then yes, please add
it with default off for now.
Thanks,
Stefan
next prev parent reply other threads:[~2021-09-24 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 15:00 [PATCH v6 0/3] arm64: Add optimized memset/memcpy/memove functions Stefan Roese
2021-09-02 15:00 ` [PATCH v6 1/3] arm64: arch/arm/lib: Add optimized memset/memcpy/memmove functions Stefan Roese
2021-09-24 14:14 ` Tom Rini
2021-09-02 15:00 ` [PATCH v6 2/3] arm64: memset-arm64: Use simple memset when cache is disabled Stefan Roese
2021-09-24 14:14 ` Tom Rini
2021-09-02 15:00 ` [PATCH v6 3/3] arm64: Kconfig: Enable usage of optimized memset/memcpy/memmove Stefan Roese
2021-09-23 19:56 ` Tom Rini
2021-09-24 7:21 ` Stefan Roese [this message]
2021-09-24 14:14 ` Tom Rini
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=f34ea18c-d636-fac8-0570-291c874236e1@denx.de \
--to=sr@denx.de \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.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