From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/wpewebkit: disable JIT for all MIPS CPUs
Date: Fri, 23 Aug 2024 16:56:40 +0200 [thread overview]
Message-ID: <20240823165640.6f40aa58@windsurf> (raw)
In-Reply-To: <20240823122919.3325906-1-aperez@igalia.com>
Hello Adrian,
On Fri, 23 Aug 2024 15:29:16 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:
> -# JIT is not supported for MIPS r6, but the WebKit build system does not
> -# have a check for these processors. The same goes for ARMv5 and ARMv6.
> -# Disable JIT forcibly here and use the CLoop interpreter instead.
> +# JIT is not supported for MIPS, ARMv5, and ARMv6, but the WebKit build
> +# system does not have a check for these processors.
> #
> +# Disable JIT forcibly here and use the CLoop interpreter instead.
> # Also, we have to disable the sampling profiler and WebAssembly, which
> # do NOT work with ENABLE_C_LOOP.
> #
> -# Upstream bugs: https://bugs.webkit.org/show_bug.cgi?id=191258
> -# https://bugs.webkit.org/show_bug.cgi?id=172765
> -# https://bugs.webkit.org/show_bug.cgi?id=265218
> +# Upstream bug: https://bugs.webkit.org/show_bug.cgi?id=278559
> #
> -ifeq ($(BR2_ARM_CPU_ARMV5)$(BR2_ARM_CPU_ARMV6)$(BR2_MIPS_CPU_MIPS32R6)$(BR2_MIPS_CPU_MIPS64R6),y)
> +ifeq ($(BR2_ARM_CPU_ARMV5)$(BR2_ARM_CPU_ARMV6)$(BR2_mips)$(BR2_mipsel),y)
But then do we actually need a change?
Keep in mind that here we are only disabling JIT explicitly for ARMv5,
ARMv6 and MIPS32R6/MIPS64R6 because they were misdetected as supported
by wpewebkit. Indeed wpewekit supported ARM and MIPS, but not some
variants of it.
For all other architectures, we do nothing, and wpewebit properly
decides whether it supports JIT or not. So if JIT support for MIPS has
been dropped I believe the correct change is:
-ifeq ($(BR2_ARM_CPU_ARMV5)$(BR2_ARM_CPU_ARMV6)$(BR2_MIPS_CPU_MIPS32R6)$(BR2_MIPS_CPU_MIPS64R6),y)
+ifeq ($(BR2_ARM_CPU_ARMV5)$(BR2_ARM_CPU_ARMV6),y)
but only of course once we use a version of wpewebkit that really has
dropped MIPS support.
As such, your change would potentially break: it re-enables JIT on
BR2_MIPS_CPU_MIPS64R6=y, because you disable for BR2_mips and
BR2_mipsel but there are the 32-bit variants of MIPS, and so
BR2_MIPS_CPU_MIPS64R6=y would again allow JIT.
Could you clarify if we have already updated to a version of wpewebkit
that has dropped MIPS support for JIT? If so, we should simply apply
the simpler change above.
Thanks!
Thomas
--
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
next prev parent reply other threads:[~2024-08-23 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 12:29 [Buildroot] [PATCH] package/wpewebkit: disable JIT for all MIPS CPUs Adrian Perez de Castro
2024-08-23 14:56 ` Thomas Petazzoni via buildroot [this message]
2024-09-02 20:29 ` Adrian Perez de Castro
-- strict thread matches above, loose matches on Subject: below --
2026-02-28 19:49 Adrian Perez de Castro
2026-03-01 14:03 ` Peter Korsgaard
2026-03-06 19:53 ` Thomas Perale via buildroot
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=20240823165640.6f40aa58@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--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