All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain <ju.o@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 1/2] package/highway: new package
Date: Thu, 24 Nov 2022 21:59:07 +0100	[thread overview]
Message-ID: <9763033b48c01a0c1869b9fffae775d8@free.fr> (raw)
In-Reply-To: <20221123151715.4a454fed@windsurf>

Hi Thomas,

On 23/11/2022 15:17, Thomas Petazzoni wrote:
> Hello Julien,
> 
> On Tue, 22 Nov 2022 22:55:56 +0100
> Julien Olivain <ju.o@free.fr> wrote:
> 
>> diff --git a/package/highway/Config.in b/package/highway/Config.in
>> new file mode 100644
>> index 0000000000..f9a0bc910c
>> --- /dev/null
>> +++ b/package/highway/Config.in
>> @@ -0,0 +1,42 @@
>> +config BR2_PACKAGE_HIGHWAY_ARCH_SUPPORTS
>> +	bool
>> +	# Supports all BR architectures by default, with few exceptions
>> +	default y
>> +	# Armv7 support is only with fpv4, see:
>> +	# https://github.com/google/highway/blob/1.0.1/CMakeLists.txt#L221
>> +	depends on !BR2_arm || BR2_ARM_FPU_VFPV4
> 
> Hm, I suppose if it works on other weird architectures, it must have a
> non-optimized version, that could work on ARM platforms that do not
> have a VFPv4 ?

You are right! There is apparently an issue in the package on
detection of arm without VFPv4. I initially wrote this package recipe
for highway-1.0.1. I then updated it to 1.0.2 which seems to have
relaxed some restrictions (incl. RISC-V 32bit). I'll investigate how
those limitations can be removed and send an updated version of this
patch.

>> +ifeq ($(BR2_ARM_FPU_VFPV4),y)
>> +HIGHWAY_CONF_OPTS += -DHWY_CMAKE_ARM7=ON
>> +else
>> +HIGHWAY_CONF_OPTS += -DHWY_CMAKE_ARM7=OFF
>> +endif
> 
> So even with -DHWY_CMAKE_ARM7=OFF, it doesn't work for ARMv5, or ARMv7
> without VFPv4 ?
> 
>> diff --git a/support/testing/tests/package/test_highway.py 
>> b/support/testing/tests/package/test_highway.py
> 
> Runtime tests coming together with the new package: excellent!

Yes, this test infra is fun! If I manage to remove the arch
limitations discussed above, I'll also rewrite this test to use the
default armv5 config...

> Thomas

Thanks for the review!
Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-11-24 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 21:55 [Buildroot] [PATCH next 1/2] package/highway: new package Julien Olivain
2022-11-22 21:59 ` [Buildroot] [PATCH next 2/2] package/libjxl: " Julien Olivain
2022-11-23 14:37   ` Thomas Petazzoni via buildroot
2022-11-24 21:03     ` Julien Olivain
2022-11-23 14:17 ` [Buildroot] [PATCH next 1/2] package/highway: " Thomas Petazzoni via buildroot
2022-11-24 20:59   ` Julien Olivain [this message]

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=9763033b48c01a0c1869b9fffae775d8@free.fr \
    --to=ju.o@free.fr \
    --cc=buildroot@buildroot.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.