Announcement

Collapse
No announcement yet.

Apple Implements LLVM JIT Back-End For WebKit JavaScript

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Apple Implements LLVM JIT Back-End For WebKit JavaScript

    Phoronix: Apple Implements LLVM JIT Back-End For WebKit JavaScript

    For speeding up the JavaScript performance within upstream WebKit, Apple developers have implemented a new just-in-time (JIT) back-end that's based upon LLVM...

    http://www.phoronix.com/vr.php?view=MTY4OTY

  • #2
    Faster Than Light (FTL) would have been a better name than Fourth Tier LLVM.

    Comment


    • #3
      Originally posted by Harsh View Post
      Faster Than Light (FTL) would have been a better name than Fourth Tier LLVM.
      Suddenly, indie gamers.

      Comment


      • #4
        Blink?

        Is this thing likely to appear in Blink?

        Comment


        • #5
          Originally posted by seedo View Post
          Is this thing likely to appear in Blink?
          That would be a no. This is JavaScriptCore, even when Chrome was using WebKit they were not using JavaScriptCore but V8. Also considering it only gives a speed-up of 20% in exchange for massive memory usage increase, bundling a full compiler, big increase in complexity and several manyears of work; FTL doesn't even look that great.

          Comment


          • #6
            I hope it can be disabled configure-time then.

            Comment


            • #7
              Originally posted by carewolf View Post
              Also considering it only gives a speed-up of 20% in exchange for massive memory usage increase, bundling a full compiler, big increase in complexity and several manyears of work; FTL doesn't even look that great.
              What are you basing any of that on?

              Comment


              • #8
                Originally posted by carewolf View Post
                That would be a no. This is JavaScriptCore, even when Chrome was using WebKit they were not using JavaScriptCore but V8. Also considering it only gives a speed-up of 20% in exchange for massive memory usage increase, bundling a full compiler, big increase in complexity and several manyears of work; FTL doesn't even look that great.
                Did someone pee in your cereal this morning or are you an Internet Explorer developer?

                Comment


                • #9
                  Originally posted by wizard69 View Post
                  Did someone pee in your cereal this morning or are you an Internet Explorer developer?
                  I am a WebKit developer. Though my perception of FTL might be tainted by the fact that when it was merged in July 2013, it managed to break everything. JavaScriptCore was unusable for more than a month after the FTL merge even though FTL was not even enabled. Not really the best of starts and it lowered my expectations of FTL dramatically (plus demonstrated the cost of added complexity even when disabled).

                  Comment


                  • #10
                    Originally posted by scottishduck View Post
                    What are you basing any of that on?
                    The webkit developers behind it are saying it will be a 33% increase. (Over the existing 3rd tier compiler). 40 times faster than interpreted vs. the 30 times faster they can already go.

                    That really just brings them back on par with their competition, it's not like this is a huge breakthrough, at least in performance. Maybe now that they've got the framework done they'll be able to get some more benefits from it soon, though.

                    Comment

                    Working...
                    X