https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70127
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 37919 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37919&action=edit the log file No, I've logged just BITS_PER_WORD, main_input_filename and current_function_name () in addition to the results of the 3 calls. I could have tried libbacktrace, the problem is that I would then need to use some locking on the append file to avoid dumps from concurrent processes overlap each other. In any case, the statistics gathering patch is attached above, so anybody can tweak it further later on.
