All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2/next 3/4] webkitgtk: update to version 2.20.0
Date: Tue, 10 Apr 2018 23:22:40 +0200	[thread overview]
Message-ID: <20180410232240.615a6dc3@windsurf> (raw)
In-Reply-To: <20180410201830.GH19381@momiji>

Hello,

On Tue, 10 Apr 2018 20:18:30 +0100, Adrian Perez de Castro wrote:

> > OK, thanks for the clarification.  
> 
> Also, I have found out from one of my test builds that in both 2.20.x releases
> we have an ugly regression of the JSC JIT support on 32-bit MIPS and ARM when
> using the softfp ABI.
> 
> A patch for this is at https://bugs.webkit.org/show_bug.cgi?id=183786 but we
> (the WebKitGTK upstream) haven't decided yet whether it will be in the next
> 2.20.x release. Some of us think it is worth a try, so I am in the middle of
> backporting the patch (and a few other patches needed by it) on top of 2.20.1,
> to include them in Buildroot, which is a good way of trying getting to try
> them on top of 2.20.1 and decide if they will go in a release as well.
> 
> If you think it would be better to first disable JIT for 32-bit ARM and MIPS
> when doing the webkitgtk package version bump, and later on re-enabling it
> with the backpoted changes, please let me know.

Since I don't know what is the extent of the breakage, and I have a
limited understanding of WebkitGtk anyway, I'll let you decide what is
best.

By "softfp ABI", are you talking soft-float (i.e the hardware has no
FPU at all) or about -mfloat-abi=softfp on ARM, which means that the
FPU may be used, but that integer registers are used to pass floating
point arguments ?

In either case, it would mean that ARM EABIhf is not broken, and
therefore JIT should be not be disabled for all ARM configurations, but
only the ones using softfp.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-04-10 21:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 18:59 [Buildroot] [PATCH v2/next 0/4] Update WebKitGTK+ to 2.20.0 Adrian Perez de Castro
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 1/4] brotli: new package Adrian Perez de Castro
2018-03-24 10:45   ` Peter Korsgaard
2018-04-02 20:25   ` Thomas Petazzoni
2018-04-02 22:07     ` Adrian Perez de Castro
2018-04-02 22:30       ` Peter Korsgaard
2018-04-03 17:15         ` Adrian Perez de Castro
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 2/4] woff2: " Adrian Perez de Castro
2018-03-24 10:48   ` Peter Korsgaard
2018-05-09  8:54   ` Thomas Petazzoni
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 3/4] webkitgtk: update to version 2.20.0 Adrian Perez de Castro
2018-03-24 10:51   ` Peter Korsgaard
2018-04-10  7:53     ` Thomas Petazzoni
2018-04-10 15:54       ` Adrian Perez de Castro
2018-04-10 15:57         ` Thomas Petazzoni
2018-04-10 16:18           ` Adrian Perez de Castro
2018-04-10 18:55             ` Thomas Petazzoni
2018-04-10 19:18               ` Adrian Perez de Castro
2018-04-10 21:22                 ` Thomas Petazzoni [this message]
2018-04-10 22:06                   ` Adrian Perez de Castro
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 4/4] webkitgtk: Add upstream patch for better memory monitoring Adrian Perez de Castro
2018-05-02  7:23 ` [Buildroot] [PATCH v2/next 0/4] Update WebKitGTK+ to 2.20.0 Thomas Petazzoni

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=20180410232240.615a6dc3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.