Closed Bug 546171 Opened 14 years ago Closed 14 years ago

lirasm: move VerboseWriter to the end of the pipeline

Categories

(Core Graveyard :: Nanojit, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: n.nethercote, Assigned: n.nethercote)

Details

(Whiteboard: fixed-in-nanojit, fixed-in-tracemonkey)

Attachments

(1 file)

lirasm's VerboseWriter is currently at the start of the pipeline.  With --optimize this leads to confusing output, because if an instruction is CSE'd it gets reprinted, eg:

  0 = int 0
  0 = int 0

the second 'int 0' isn't really there but the CSE filter passes back a reference to the first 'int 0' and that's what gets printed -- the same instruction gets printed twice.

Moving VerboseWriter to the end of the pipeline will fix this because the second 'int 0' won't even reach it because CseFilter won't pass it on.  This will make lirasm match TM's and TR's pipelines.
Attached patch patchSplinter Review
Attachment #426934 - Flags: review?(stejohns)
Attachment #426934 - Flags: review?(stejohns) → review+
Whiteboard: fixed-in-nanojit
http://hg.mozilla.org/tracemonkey/rev/7b1d42444f85
Whiteboard: fixed-in-nanojit → fixed-in-nanojit, fixed-in-tracemonkey
http://hg.mozilla.org/mozilla-central/rev/7b1d42444f85
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: