https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96534
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- > I did not have the real statistics yet as our company is not yet moved to > gcc9 (maybe end of this year ). > > and even the size of the compressed file is smaller , but we have to unzip > and parse it , right? it just increase the workload . Yes, but if it's problem we can start using e.g. zstd that has super-fast decompression. > > however, the stdout option ( -t ) could be very helpful , we don't need to > write to disk and just parse the stdout content. Yes, that be quite useful for your test-case. Or you may consider using: https://github.com/RPGillespie6/fastcov > > well, I also notice that the "function_name" in "lines" object is mangled > even I use "--demangled-names" option, can you print the demangled_name when > "-m" option given ? ( yes I know there is demangled name in "functions" part > ) . the reason is: we need to know the exact function name and it's lines, > in current format , we have to find all demangled function name and it's > start and end line number, then check the lines part to assign each lines > into functions . It's handy to use mangled name as a unique key from "lines" to "functions".
