Closed Bug 2003226 Opened 11 months ago Closed 11 months ago

riscv64: MacroAssembler::wasmCheckSlowCallsite doesn't account for `jal` sequence length

Categories

(Core :: JavaScript Engine: JIT, defect, P5)

Product:
Core
Component:
JavaScript Engine: JIT
Platform:
RISCV64
Unspecified
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
148 Branch
Tracking Flags:
Tracking Status
firefox148 --- fixed

People

(Reporter: csmantle, Assigned: csmantle)

References

(Blocks 1 open bug)

Details

Attachments

(1 external file)

This is caught by jsapi-tests testWasmCheckSlowCallMarkerHit.

Link: https://ci.rvperf.org/job/Spidermonkey-upstream-fast-check/15356/console#:~:text=testWasmCheckSlowCallMarkerHit

Assignee: nobody → webmaster
Hardware: Unspecified → RISCV64
Status: NEW → ASSIGNED
Blocks: sm-riscv64
Severity: -- → S4
Priority: -- → P5
Pushed by rhunt@eqrion.net: https://github.com/mozilla-firefox/firefox/commit/4c851cb40c56 https://hg.mozilla.org/integration/autoland/rev/d4a68c1236ec [riscv64] Account for jal sequence length when extracting slow call marker. r=nbp,rhunt

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

Status: ASSIGNED → RESOLVED
Closed: 11 months ago
status-firefox148: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 148 Branch
QA Whiteboard: [qa-triage-done-c149/b148]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: