Results 1 to 10 of 14

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

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,327

    Default 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. #2
    Join Date
    Feb 2010
    Posts
    11

    Default

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

  3. #3
    Join Date
    Nov 2012
    Location
    France
    Posts
    536

    Default

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

  4. #4
    Join Date
    Mar 2013
    Location
    Kerala, India
    Posts
    11

    Question Blink?

    Is this thing likely to appear in Blink?

  5. #5
    Join Date
    Nov 2012
    Posts
    143

    Default

    Quote 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.

  6. #6
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,988

    Default

    I hope it can be disabled configure-time then.

  7. #7
    Join Date
    Jun 2011
    Location
    Scotland
    Posts
    101

    Default

    Quote 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?

  8. #8
    Join Date
    Sep 2009
    Posts
    313

    Default

    Quote 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?

  9. #9
    Join Date
    Mar 2013
    Posts
    44

    Default

    Quote 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.
    This seems like an extraordinarily ignorant statement.
    - LLVM as a JIT has been a focus of attention for a long time because it's of interest to lots of people. There may be several man-years of work there, but it's work that would have happened regardless of what WebKit did. So WebKit might as well take advantage of it.
    Such complexity as has been added to WebKit is complexity that should be added anyway; it's OBVIOUSLY the right thing to do to move JIT'ing onto a second thread that runs while the interpreter runs, and doing this with the FTL JIT lays the ground work for doing it in many other situations. EVERY bit of such work work, whether it's running the first tier JIT or the CSS compiler, should be spawned off to secondary threads as the same time as we start by using an immediate interpreter to get things going.

    - "massive memory usage increase " is no big deal in many circumstances. Plenty of people have multiple GB of RAM available, which most of the time is being used to cache files that were last touched two weeks ago. What's wrong with using that RAM to speed things up by 20%?

    - "bundling a full compiler" is a problem why, exactly? So the Safari binary is now 1MB larger. WTF cares?

    It's fine to argue about technical direction; that's what tech sites are about. But you come across as a ignorant luddite who just seems pissed off that things have changed. "Life was great when everyone used a JIT that I could understand, but I don't understand this newfangled LLVM stuff so obviously it six".

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •