https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961
--- Comment #23 from xaizek ---
> it should be fixed in the updated version of the patch.
Yes, it is.
> Right now, one can easily detect JSON format with
> `gcov --help | grep json-format`, am I right? What type of capability would
> you apprec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961
--- Comment #20 from xaizek ---
The patch works! I think you actually implemented behaviour of `-p` for `-l`
(you hash path in the code and don't process includes). `-l` doesn't seem to
make much sense for JSON, because all includes will be in th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961
--- Comment #18 from xaizek ---
> The following 2 files should be created (right now b.gcov.json.gz and
> a.gcov.json.gz are created)
>
> b.gcov.json.gz
> src/a.gcov.json.gz
>
> and so -p and -x does not play any role here.
Now you'll need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961
--- Comment #15 from xaizek ---
> I don't think anything is violated, because GCC has `-o` option.
Actually, I tried it and GCC can produce such weird results as well, but
documentation talks about file discovery, not about reproducing this beha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961
--- Comment #14 from xaizek ---
> This example violates that because you would end up with clasing myclass.o.
I don't think anything is violated, because GCC has `-o` option. It's
equivalent in GCOV is mangling:
> The mangledname part of the ou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961
xaizek changed:
What|Removed |Added
CC||xaizek at posteo dot net
--- Comment #11 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56549
xaizek at posteo dot net changed:
What|Removed |Added
CC||xaizek at posteo dot net
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: xaizek at posteo dot net
Target Milestone: ---
Source code to reproduce the ICE
// no ICE if triggerBug is not a template
template
struct
