Closed
Bug 490414
Opened 16 years ago
Closed 16 years ago
Need a -Dforcejit switch
Categories
(Tamarin Graveyard :: Baseline JIT (CodegenLIR), defect)
Tamarin Graveyard
Baseline JIT (CodegenLIR)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: lhansen, Assigned: lhansen)
Details
Attachments
(1 file)
|
4.17 KB,
patch
|
edwsmith
:
review+
|
Details | Diff | Splinter Review |
I need a way to force jitting of all code in such a way that failure to jit a piece of code will result in a fatal error (abort). I'm proposing a -Dforcejit switch for this.
The reason is that -Ojit will silently fall back on the interpreter in some cases, and I need to know whether particular test cases (notably the instruction set tests written in assembler) are run in both the jit and the interpreter. (As it is, I suspect very strongly that some of those tests are always interpreted.)
|
||
Comment 1•16 years ago
|
||
-Ojitordie ? forcejit doesn't quite convey what is going to happen.
|
|
Assignee | |
Comment 2•16 years ago
|
||
The name of the switch is -Djitordie (-D since it's only useful for debugging; jitordie because, but as Rick says, forcejit doesn't quite capture it).
As I predicted it reveals that the 'I' asm regression tests won't be jitted. Nor will 33 other files in the test suite...
|
|
||
Updated•16 years ago
|
Attachment #375619 -
Flags: review?(edwsmith) → review+
|
|
Assignee | |
Comment 3•16 years ago
|
||
redux changeset d146ad8ccf12
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
|
|
||
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•