Open
Bug 1896833
Opened 1 year ago
Updated 6 days ago
Add printf opcode for debugging
Categories
(Core :: JavaScript Engine: JIT, task, P5)
Core
JavaScript Engine: JIT
Tracking
()
NEW
People
(Reporter: yulia, Assigned: yulia)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Sometimes masm.printf isn't enough for debugging what is going on in JITs. I introduced the printf opcode for my own purposed, to record critical loop variables (variables that control the behavior of the loop), but it may be more broadly useful.
Assignee | ||
Updated•1 year ago
|
Severity: -- → S4
Priority: -- → P5
Comment 1•1 year ago
|
||
Fwiw, I've thought about adding something like this too, I've ended up repurposing JSOp::Debugger for similar things in the past.
Assignee | ||
Comment 2•1 year ago
|
||
This introduces LIR and MIR opcodes, as well as specialization for different MIRTypes with regards
to what gets printed. I added a Printf2 method, because it can be quite frustrating trying to figure
out what part of a string printed from a register is the actual string. I didn't handle dependent
strings at all, those can be added later.
Updated•9 months ago
|
Blocks: sm-runtime
Updated•6 days ago
|
Severity: S4 → N/A
You need to log in
before you can comment on or make changes to this bug.
Description
•