1922499 - Use VirtualRegister::firstRange instead of rangeFor in a few places

Status: RESOLVED FIXED

(Core :: JavaScript Engine: JIT, task, P1)

Description

[Jan de Mooij [:jandem]]

There are some places where we call VirtualRegister::rangeFor but we just want to get the virtual register's first range. VirtualRegister::rangeFor does a binary search so is also fast, but is still slower than just getting the first range.

Comment 1

[Jan de Mooij [:jandem]]

Attachment: Bug 1922499 - Use VirtualRegister::firstRange instead of rangeFor in a few places. r?jseward!

This changes some places to use firstRange instead of rangeFor. This is a little
faster but it's also clearer about what the code is doing.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/bee25281b27a
Use VirtualRegister::firstRange instead of rangeFor in a few places. r=jseward

Comment 3

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/bee25281b27a