It doesn't actually matter for the hazard analysis itself, since RunScript and friends can already GC and having the JSNative in the graph doesn't help. But it's kind of useful for other callgraph uses.

Comment on attachment 8996508 [details] [diff] [review] Synthesize call edges from Interpret and EnterJit to all JSNatives Review of attachment 8996508 [details] [diff] [review]: ----------------------------------------------------------------- Yes, makes sense. ::: js/src/devtools/rootAnalysis/computeCallgraph.js @@ +289,5 @@ > + JSNatives.push(functionName); > +} > + > +function postprocess_callgraph() { > + for (const caller of Object.keys(JSNativeCaller)) { Could use a comment to say what this is doing.

Pushed by sfink@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/c22b643cdf51 Synthesize call edges from Interpret and EnterJit to all JSNatives, r=jonco

Backout by sfink@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/06ffaf98e1e9 Backed out changeset c22b643cdf51 (bug 1479961, bug 1480129)

Pushed by sfink@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/113e7326a16a Synthesize call edges from Interpret and EnterJit to all JSNatives, r=jonco