JSFRAME_ASSIGNING is only used to tell js_InferFlags we are assigning. This can be done more simply the way everywhere else does it: with JSAutoResolveFlags. This came up in the context of bug 645901 when I was looking for places where we unnecessarily twiddle frame flags (thereby requiring frame deoptimization).
Created attachment 525512 [details] [diff] [review] do it
Attachment #525512 - Flags: review?(dvander)
Comment on attachment 525512 [details] [diff] [review] do it >+ uint32 opFormat = cs->format; Nit: format is the canonical name elsewhere. >+ uint32 setPropFlags = JOF_MODE(opFormat) == JOF_NAME Nit: we follow K&R and parenthesize lower-than-unary-precedence ?: conditions. JSFRAME_flagls: one down, 21 to go! :-P /be
Ah, good to know. I doubt the flags will be dying any time soon (bug 645901 will avoid even storing them!), but the thing I'd really like to see go are these resolve flags. Unfortunately, it seems like DOM global window quirks really want them...
Comment on attachment 525512 [details] [diff] [review] do it nice
Attachment #525512 - Flags: review?(dvander) → review+
Whiteboard: fi → fiixed-in-tracemonkey
Whiteboard: fiixed-in-tracemonkey → fixed-in-tracemonkey
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.