https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113528
--- Comment #3 from Andrew Pinski ---
>Fragment N6
So in the tools GCC's code that currenly use gcov_read_profile_dir is not a
leak that matters because the program exits if that fails. So it is only an
issue if someone externally uses it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113528
--- Comment #2 from Andrew Pinski ---
> Fragment N3
The number of json::array leaked is 2 per argument to gcov. Not enough to care
about since it exits after it finishes. If you are passing 1000 files to gcov
well you have other issues to star
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113528
--- Comment #1 from Andrew Pinski ---
> Fragment N4
Is NOT an issue, based on all of the uses of add_char, the character is tested
before adding it ...
And there 256 can hold all values of signed char.
>Fragment N5
Is just a small codiing st
