subject:"\[Bug gcov\-profile\/93623\] No need to dump gcdas when forking"

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-06-08 Thread marxin at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #12 from Martin Liška --- (In reply to calixte from comment #11) > Why did you remove __gcov_flush ? It is not a supported __gcov_* library call: https://gcc.gnu.org/onlinedocs/gcc/Gcov-and-Optimization.html You should rather call _

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-06-03 Thread cdenizet at mozilla dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #11 from calixte --- Why did you remove __gcov_flush ? FYI, we use it in Firefox to dump counters on SIGUSR1: https://searchfox.org/mozilla-central/source/tools/code-coverage/CodeCoverageHandler.cpp#49

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-05-05 Thread cvs-commit at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #9 from CVS Commits --- The master branch has been updated by Martin Liska : https://gcc.gnu.org/g:811b7636cb8c10f1a550a76242b5666c7ae36da2 commit r11-85-g811b7636cb8c10f1a550a76242b5666c7ae36da2 Author: Martin Liska Date: Tue Ma

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-05-05 Thread cvs-commit at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #8 from CVS Commits --- The master branch has been updated by Martin Liska : https://gcc.gnu.org/g:c0532db47d092430f8e8f497b2dc53343527bb13 commit r11-84-gc0532db47d092430f8e8f497b2dc53343527bb13 Author: Martin Liska Date: Tue Ma

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-05-05 Thread cvs-commit at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #7 from CVS Commits --- The master branch has been updated by Martin Liska : https://gcc.gnu.org/g:d39f7dc8d558ca31a661b02d08ff090ce65e6652 commit r11-83-gd39f7dc8d558ca31a661b02d08ff090ce65e6652 Author: Martin Liska Date: Tue Ma

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-05-05 Thread marxin at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 Martin Liška changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-02-21 Thread cdenizet at mozilla dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #6 from calixte --- (In reply to Alexander Monakov from comment #5) > (In reply to calixte from comment #2) > > I think the reset is useless in the case of exec** functions since the > > counters are lost when an exec** is called. So

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-02-21 Thread amonakov at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 Alexander Monakov changed: What|Removed |Added CC||amonakov at gcc dot gnu.org --- Comm

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-02-21 Thread marxin at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #4 from Martin Liška --- Both comments are valid to me!

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-02-21 Thread cdenizet at mozilla dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #3 from calixte --- And about fork, no need to lock when resetting in the child process since we've only one thread.

[Bug gcov-profile/93623] No need to dump gcdas when forking

2020-02-21 Thread cdenizet at mozilla dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93623 --- Comment #2 from calixte --- I think the reset is useless in the case of exec** functions since the counters are lost when an exec** is called. So it can probably be removed too.