On Oct 28, 2019, Richard Biener <rguent...@suse.de> wrote: > I guess you need to elaborate on 'per-file'. With LTO as far as I > understand you'll get the graph per LTRANS unit (did you check > where the output is generated?).
Yeah, I guess this was not designed with LTO in mind; it probably even predates LTO. We get per-LTRANS unit indeed, and the output is generated in the temporary dir, which is not desirable behavior for sure. The outputs seem to be usable if you can figure out what they are, but I'm not sure how to go about combining the multiple .ci files, or how to name the combined output, since it's not generally expected that these files will be created at link time, rather than at compile time. I'll bring this up internally and come back with some improvement. > Is this mainly a debugging tool or does it serve a different purpose? It feeds gnatstack, that's a tool to compute max stack depth and perform other call graph analyzes. I don't think of it as a debugging tool. https://www.adacore.com/gnatpro/toolsuite/gnatstack http://docs.adacore.com/live/wave/gnatstack/html/gnatstack_ug/index.html -- Alexandre Oliva, freedom fighter he/him https://FSFLA.org/blogs/lxo Be the change, be Free! FSF VP & FSF Latin America board member GNU Toolchain Engineer Free Software Evangelist Hay que enGNUrecerse, pero sin perder la terGNUra jamás - Che GNUevara
