Labels
Posted by on Labels:

Next JIT branch up


There hasn't been a lot of activity on Talospace because I've been busy on other OpenPOWER stuff. The POWER9 Firefox JIT has been transplanted to Firefox 97 (on a new branch) and compiles, links and basically runs (in the previous non-Ion configuration). Once the test suite is passing again, it's time to work on the final optimizing compiler stage hopefully in time to make Firefox 102 and the next ESR. You can help.
Email Post

Comments

  1. Dan HorákFebruary 9, 2022 at 4:31 AM

    Souns like I could do a JIT-enabled build in COPR for FF 97, awesome. Thus it would get even more testing.

    ReplyDelete
  2. ClassicHasClassFebruary 9, 2022 at 9:18 AM

    Potentially, though the test suite is not passing yet, so there will probably be assertions or crashes. I've already sniffed out a couple regressions related to new code paths the old code didn't hit.

    ReplyDelete
  3. Niccolò BelliFebruary 16, 2022 at 4:13 AM

    I would be interested in enabling JIT for the gentoo ebuild as well, but enabling the sandbox is higher on my priority list. Are you aware of any patches to do so for ppc64le? https://bugzilla.mozilla.org/show_bug.cgi?id=1754959

    ReplyDelete
    Replies
    1. ClassicHasClassFebruary 16, 2022 at 10:32 AM

      I haven't seen any. I'll look at it. Thanks!

      Delete
    2. Niccolò BelliFebruary 26, 2022 at 3:09 AM

      Btw do you use gcc or clang to build Firefox? Because I had to apply patches to successfully build it with clang and I'm still getting this weird message at startup: https://bugzilla.mozilla.org/show_bug.cgi?id=1757271

      Delete
    3. ClassicHasClassFebruary 26, 2022 at 9:18 AM

      I use, and prefer, gcc. I got that exact message when building Firefox 97 with clang (see that post). A gcc build was just fine.

      Delete

Post a Comment

Comments are subject to moderation. Be nice.