Currently the profiling API dump a text version of the assembly with jsfriendapi functions. This API expose the compilation graph in a human friendly text format, and not a computer friendly format. The Debugger.onIonCompilation hook expose the last MIR / LIR graph, and already has a computer-friendly format, which can be exposed in a human-friendly manner [1]. We should separate the assembly output provided by the current profiling API (IonScriptCounts / IonBlockCounts) from the hit-counts. And move the assembly dump to the Debugger.onIonCompilation hook. Then we should maybe merge the hit-counts with the JSScript hit-counts. Note that the initial goal of this profiling API was to associate the hit-counts with each compilation result, so we should probably keep this feature as a separate profiling mode. [1] https://github.com/nbp/jit-dev-tools

onIonCompilation is gone (Bug 1245860)