1479965 - [hazard] Use mangled names everywhere

Status: RESOLVED FIXED

(Core :: JavaScript: GC, enhancement, P3)

Description

[Steve Fink [:sfink] [:s:]]

I continue to have missing callgraph edges because the calling side and the called side have slightly different names for types.

Comment 1

[Steve Fink [:sfink] [:s:]]

Attachment: Use mangled names everywhere, recording unmangled names for pattern matching and human-readable outputs

Do what I should have done long ago: use mangled names everywhere, recording unmangled names for pattern matching and human-readable outputs.

Comment 2

[Jon Coppeard (:jonco)]

Comment on attachment 8996515 [details] [diff] [review]
Use mangled names everywhere, recording unmangled names for pattern matching and human-readable outputs

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

::: js/src/devtools/rootAnalysis/computeCallgraph.js
@@ +29,5 @@
> +    if (id !== undefined)
> +        return id;
> +
> +    id = memoized.size + 1;
> +    memoized.set(name, "" + id);

I'm not sure why you're doing |"" + id| here.

@@ +39,1 @@
>  function memo(name)

memo and memo_data could use some more descriptive names.

Comment 3

[Steve Fink [:sfink] [:s:]]

(In reply to Jon Coppeard (:jonco) from comment #2)
> Comment on attachment 8996515 [details] [diff] [review]
> Use mangled names everywhere, recording unmangled names for pattern matching
> and human-readable outputs
> 
> Review of attachment 8996515 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> ::: js/src/devtools/rootAnalysis/computeCallgraph.js
> @@ +29,5 @@
> > +    if (id !== undefined)
> > +        return id;
> > +
> > +    id = memoized.size + 1;
> > +    memoized.set(name, "" + id);
> 
> I'm not sure why you're doing |"" + id| here.

I don't remember exactly, but I think it was because I wrote out a JSON data structure containing ids, then read it back into Python. I also read in callgraph.txt, parsing it by splitting up a string or perhaps parsing it with a regex. Lookups on the table I built from the regex never found any of the things I read in from the JSON, because the JSON ids were numbers but the parsed ids were strings. So I decided to make ids always be strings.

I guess it would be better to go the other way and make ids always be integers. It should use a bit less memory.

> @@ +39,1 @@
> >  function memo(name)
> 
> memo and memo_data could use some more descriptive names.

Agreed, I'll rename them.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/a188327354ab
Use mangled names everywhere, recording unmangled names for pattern matching and human-readable outputs, r=jonco

Comment 5

[Stefan Hindli [:stefan_hindli]]

https://hg.mozilla.org/mozilla-central/rev/a188327354ab