Closed Bug 349802 Opened 18 years ago Closed 18 years ago

"x;" (where x is a function) is eliminated only during second pass through decompilation due to {} block

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
RESOLVED DUPLICATE of bug 349634

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: testcase) 

> function () { { function x() { }; x; } }
function () { function x() { } x; }

> function () { function x() { } x; }
function () { function x() { } }

Expected: the "x;" statement should be eliminated on the first pass, or not at all.  My fuzzer in bug 349611 doesn't like it when functions change during a round-trip through uneval.

This might be related to bug 349634 (or it's possible that a fix for bug 349634 would mask this bug).
Summary: "x;" (where x is a function) is eliminated only during second pass through decompilation → "x;" (where x is a function) is eliminated only during second pass through decompilation due to {} block
Just a dup -- loss of braces causes the rest according to correct optimizations.

/be

*** This bug has been marked as a duplicate of 349634 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.