Closed Bug 918321 Opened 11 years ago Closed 11 years ago

Remove some dead code from the JS engine

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla27

People

(Reporter: ehsan.akhgari, Assigned: sfink)

References

Details

Attachments

(2 files)

Attached patch Patch (v1)Splinter Review
Discovered by clang.
Attachment #807190 - Flags: review?(luke)
Comment on attachment 807190 [details] [diff] [review]
Patch (v1)

Thanks!
Attachment #807190 - Flags: review?(luke) → review+
Comment on attachment 807190 [details] [diff] [review]
Patch (v1)

Review of attachment 807190 [details] [diff] [review]:
-----------------------------------------------------------------

::: js/src/jit/MIR.h
@@ +8454,5 @@
>  
>  class MAsmJSLoadGlobalVar : public MNullaryInstruction
>  {
>      MAsmJSLoadGlobalVar(MIRType type, unsigned globalDataOffset, bool isConstant)
> +      : globalDataOffset_(globalDataOffset)

Seems like the isConstant parameter is dead now too.
Or would this be useful information in the future?
Attachment #807327 - Flags: review?(luke)
Assignee: ehsan → sphink
Let's check with Douglas: are there some pending patches that will be using isConstant?
Flags: needinfo?(dtc-moz)
https://hg.mozilla.org/mozilla-central/rev/04bf94160337
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
The lack of use of isConstant might be a regression from
bug 877338, or it might no longer be necessary after the
patch in 877338.   It might still be possible to relax
the constraints on movement of a global load when it is
a constant.  I'll need to study the code further.
Depends on: 920452
Flags: needinfo?(dtc-moz)
Attachment #807327 - Flags: review?(luke)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: