https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96534
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to xlwu from comment #0)
> since gcc9, the gcov did not support intermediate format and replace with
> json format , our application deeply depend on intermediate format , is it
> possible to restore the intermediate format ?
No, the support was removed from the GCC.
> or could you let me know any
> workaround ?
Sure, it's very easy. One can get the very same information from the new JSON
format (which is fairly simple):
https://gcc.gnu.org/onlinedocs/gcc/Invoking-Gcov.html
>
> background :
> I am a software engineer from SNPS , we have an application that extract all
> file+functions and it's related lines per test case, and we save this data
> into DB which help us to predict the test to verify when RnD updated any
> lines in source code before their check in. we call this application as
> "smart regression".
That's a nice usage of the GCOV and the new format should simplify your life.
>
> now , when gcov move to json file, it increase the size a lot which affect
> the efficiency to parse the data
I'm aware of the limitation. Note that the JSON format is compressed with gzip.
Can you please share more statistics?
> , what's worse, we had to revise our code
> to support the new json format while we need to support the old format in
> the same time , as our company have many products and each product have many
> live branches , some of them still using gcc6 version.
I see. As mentioned, porting to the new format should be fairly simple.
>
> I tried to use older gcov version on the new gcc instructed gcda and gcno
> file , it did not work.
Please don't do it.
