public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [stage1][PATCH 0/3] __gcov_dump improvements
@ 2020-04-03  8:06 Martin Liska
  2020-04-02 14:47 ` [PATCH 1/3] Do locking for __gcov_dump and __gcov_reset as well Martin Liska
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Martin Liska @ 2020-04-03  8:06 UTC (permalink / raw)
  To: gcc-patches; +Cc: cdenizet, amonakov

Hi.

The following mini patch series improves:
- gcov run-time locking is used for user accessible __gcov_dump and __gcov_reset functions
- do not run __gcov_flush in fork, only __gcov_reset is called in child process
- gcov exec* wrappers dump counters and reset only if execv* fails

Patch can bootstrap on x86_64-linux-gnu and survives regression tests. 
I'll install the patch set in next stage1 if there are no objections.

Thanks,
Martin

Martin Liska (3):
  Do locking for __gcov_dump and __gcov_reset as well.
  Use __gcov_dump and __gcov_reset in execv and fork context.
  Remove __gcov_flush.

 gcc/tree-cfg.c             |   4 +-
 libgcc/Makefile.in         |   5 +-
 libgcc/gcov.h              |   5 --
 libgcc/libgcov-interface.c | 126 +++++++++++++++++++++++--------------
 libgcc/libgcov.h           |   6 ++
 5 files changed, 91 insertions(+), 55 deletions(-)

-- 
2.26.0


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-04-03  8:11 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-03  8:06 [stage1][PATCH 0/3] __gcov_dump improvements Martin Liska
2020-04-02 14:47 ` [PATCH 1/3] Do locking for __gcov_dump and __gcov_reset as well Martin Liska
2020-04-02 14:58 ` [PATCH 2/3] Use __gcov_dump and __gcov_reset in execv and fork context Martin Liska
2020-04-02 15:02 ` [PATCH 3/3] Remove __gcov_flush Martin Liska

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).