Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 4821f5b9446c84a641285abafd6688a5ed5571b6
      
https://github.com/WebKit/WebKit/commit/4821f5b9446c84a641285abafd6688a5ed5571b6
  Author: Keith Miller <[email protected]>
  Date:   2026-02-12 (Thu, 12 Feb 2026)

  Changed paths:
    M Source/JavaScriptCore/lol/LOLJIT.cpp
    M Source/JavaScriptCore/lol/LOLRegisterAllocator.h

  Log Message:
  -----------
  [LOL] op_new_object should not always flush
https://bugs.webkit.org/show_bug.cgi?id=307548
rdar://170148582

Reviewed by Yusuke Suzuki.

Right now we always flush for op_new_object, however since we allocate
objects its more profitable to do a normal allocation and silentSpill
on the slow path.

Also, uncovered an issue where allocating more than one scratch will
end up flushing the same stack slot twice triggering an ASSERT. Now we
lock the scratches so they can't be spilled.

No new tests, no behavior change. Covered by existing tests.

Canonical link: https://commits.webkit.org/307349@main



To unsubscribe from these emails, change your notification settings at 
https://github.com/WebKit/WebKit/settings/notifications

Reply via email to