From: Tom Rini <trini@konsulko.com>
To: Stefan Roese <sr@denx.de>
Cc: u-boot@lists.denx.de,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
sjg@chromium.org, Wolfgang Denk <wd@denx.de>
Subject: Re: [PATCH v5 3/3] arm64: Kconfig: Enable usage of optimized memset/memcpy/memmove
Date: Thu, 2 Sep 2021 10:17:22 -0400 [thread overview]
Message-ID: <20210902141722.GA15430@bill-the-cat> (raw)
In-Reply-To: <20210817084827.692859-4-sr@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
On Tue, Aug 17, 2021 at 10:48:27AM +0200, Stefan Roese wrote:
> This patch enables the use of the optimized memset(), memmove() &
> memcpy() versions recently added on ARM64.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> ---
>
> Changes in v5:
> - memmove is now auto-selected (or deselected) with the memcpy
> Kconfig selection as it's entry is the same as memcpy for ARM64
>
> Changes in v3:
> - Add memmove as well
>
> arch/arm/Kconfig | 37 +++++++++++++++++++++++++++++------
> arch/arm/include/asm/string.h | 4 ++++
> 2 files changed, 35 insertions(+), 6 deletions(-)
This gives a ton of build failures for me, using gcc-9.2.0 (from
kernel.org) along the lines of:
Building current source for 1 boards (1 thread, 16 jobs per thread)
aarch64: + j721e_evm_a72
+(j721e_evm_a72) aarch64-linux-ar: warning: arch/arm/lib/memset-arm64.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
+(j721e_evm_a72) aarch64-linux-ar: warning: arch/arm/lib/memcpy-arm64.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
+(j721e_evm_a72) aarch64-linux-ld.bfd: warning: arch/arm/lib/memset-arm64.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
+(j721e_evm_a72) aarch64-linux-ld.bfd: warning: arch/arm/lib/memcpy-arm64.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
+(j721e_evm_a72) aarch64-linux-objcopy: warning: u-boot: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
+(j721e_evm_a72) aarch64-linux-objdump: warning: u-boot: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
+(j721e_evm_a72) aarch64-linux-nm: warning: u-boot: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
+(j721e_evm_a72) tools/relocate-rela: bad rela bounds
+(j721e_evm_a72) make[1]: *** [u-boot-nodtb.bin] Error 1
+(j721e_evm_a72) make: *** [sub-make] Error 2
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-09-02 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 8:48 [PATCH v5 0/3] arm64: Add optimized memset/memcpy/memove functions Stefan Roese
2021-08-17 8:48 ` [PATCH v5 1/3] arm64: arch/arm/lib: Add optimized memset/memcpy/memmove functions Stefan Roese
2021-08-17 8:48 ` [PATCH v5 2/3] arm64: memset-arm64: Use simple memset when cache is disabled Stefan Roese
2021-08-17 8:48 ` [PATCH v5 3/3] arm64: Kconfig: Enable usage of optimized memset/memcpy/memmove Stefan Roese
2021-09-02 14:17 ` Tom Rini [this message]
2021-09-02 14:37 ` Stefan Roese
2021-09-02 14:41 ` 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=20210902141722.GA15430@bill-the-cat \
--to=trini@konsulko.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--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