[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2022-05-27 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|9.5 |---

[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2021-06-01 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|9.4 |9.5

--- Comment #6 from Richard Biener  ---
GCC 9.4 is being released, retargeting bugs to GCC 9.5.

[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2021-05-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Richard Biener  changed:

   What|Removed |Added

 Status|ASSIGNED|NEW

[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2020-09-16 Thread i at maskray dot me
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Fangrui Song  changed:

   What|Removed |Added

 CC||i at maskray dot me

--- Comment #5 from Fangrui Song  ---
I am a bit curious how GCC instruments such functions which may alter control
flows

* exit/execve/execl/etc
* fork
* functions which may throw or call any above functions

If you force a split basic block after such functions, you get counts correct
but you pay the costs that there is one more basic block and two more arcs. In
-fprofile-arcs you need to pay the instrumentation cost of one arc (after
taking into account of the Kirchhoff circuit law's spanning tree optimization).
If you assume every external function call may alter control flows, you pay
rather large overhead for things you probably care little (since I know some
underlying mechanism I don't trust line counts after special functions).

[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2020-03-12 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|9.3 |9.4

--- Comment #4 from Jakub Jelinek  ---
GCC 9.3.0 has been released, adjusting target milestone.

[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2019-08-12 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|9.2 |9.3

--- Comment #3 from Jakub Jelinek  ---
GCC 9.2 has been released.

[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2019-05-03 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|9.0 |9.2

--- Comment #2 from Jakub Jelinek  ---
GCC 9.1 has been released.

[Bug gcov-profile/85351] [GCOV] Wrong coverage with exit() executed in a if statement within a called function

2018-07-25 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85351

Martin Liška  changed:

   What|Removed |Added

   Priority|P3  |P5
   Assignee|marxin at gcc dot gnu.org  |unassigned at gcc dot 
gnu.org

--- Comment #1 from Martin Liška  ---
Confirmed, it's really small issue.