Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dimi Tomov <dimi@tpm.dev>
Cc: Ben Hutchings <ben.hutchings@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/wolfssl: Disable broken asm implementations on 32-bit Arm
Date: Fri, 22 Jul 2022 22:51:20 +0200	[thread overview]
Message-ID: <20220722225120.2472bbab@windsurf> (raw)
In-Reply-To: <20220614192445.2390329-1-ben.hutchings@mind.be>

Hello Dimi,

Could you give some feedback on the below patch that touches wolfssl?
Do me it looks good, but perhaps you want to improve something in
upstream wolfssl in relation to this issue, such as detecting the CPU
architecture capabilities automatically?

Best regards,

Thomas Petazzoni

On Tue, 14 Jun 2022 21:24:45 +0200
Ben Hutchings <ben.hutchings@mind.be> wrote:

> wolfSSL has ARMv8-A assembly implementations of some functions for
> both A64 and A32 ISAs.  However, some of the A32 versions use r11,
> which is usually not allowed:
> 
> wolfcrypt/src/port/arm/armv8-aes.c: In function 'wc_AesCbcEncrypt':
> wolfcrypt/src/port/arm/armv8-aes.c:3303:5: error: fp cannot be used in 'asm' here
>  3303 |     }
>       |     ^
> 
> That can be fixed by adding the compiler flag -fomit-frame-pointer,
> but then there is another failure:
> 
> /tmp/ccV19DQV.s: Assembler messages:
> /tmp/ccV19DQV.s:248: Error: first transfer register must be even -- `ldrd r11,r10,[r14,#4*14]'
> make[3]: *** [Makefile:5858: wolfcrypt/src/port/arm/src_libwolfssl_la-armv8-chacha.lo] Error 1
> 
> This is definitely not a valid instruction in A32, which suggests that
> this code isn't being tested at all upstream.  So disable it here.
> 
> Signed-off-by: Ben Hutchings <ben.hutchings@mind.be>
> ---
>  package/wolfssl/wolfssl.mk | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/package/wolfssl/wolfssl.mk b/package/wolfssl/wolfssl.mk
> index 58b6f296ab..ff6a65c397 100644
> --- a/package/wolfssl/wolfssl.mk
> +++ b/package/wolfssl/wolfssl.mk
> @@ -33,14 +33,12 @@ WOLFSSL_CONF_OPTS += --disable-sslv3
>  endif
>  
>  # enable ARMv8 hardware acceleration
> -ifeq ($(BR2_ARM_CPU_ARMV8A),y)
> +ifeq ($(BR2_aarch64),y)
>  WOLFSSL_CONF_OPTS += --enable-armasm
>  # the flag -mstrict-align is needed to prevent build errors caused by
>  # some inline assembly in parts of the AES structure using the "m"
>  # constraint
> -ifeq ($(BR2_aarch64),y)
>  WOLFSSL_CONF_ENV += CPPFLAGS="$(TARGET_CPPFLAGS) -mstrict-align"
> -endif
>  else
>  WOLFSSL_CONF_OPTS += --disable-armasm
>  endif



-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-07-22 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 19:24 [Buildroot] [PATCH] package/wolfssl: Disable broken asm implementations on 32-bit Arm Ben Hutchings
2022-07-22 20:51 ` Thomas Petazzoni via buildroot [this message]
2022-08-01 18:53   ` Dimi Tomov
2023-02-07 21:39 ` Thomas Petazzoni via buildroot
2023-02-28 15:34   ` Peter Korsgaard

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=20220722225120.2472bbab@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ben.hutchings@mind.be \
    --cc=dimi@tpm.dev \
    --cc=thomas.petazzoni@bootlin.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