From: Martin Liska <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: cdenizet@mozilla.com
Cc: amonakov@gcc.gnu.org
Subject: [stage1][PATCH 0/3] __gcov_dump improvements
Date: Fri, 3 Apr 2020 10:06:46 +0200 [thread overview]
Message-ID: <cover.1585901206.git.mliska@suse.cz> (raw)
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
next reply other threads:[~2020-04-03 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 8:06 Martin Liska [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1585901206.git.mliska@suse.cz \
--to=mliska@suse.cz \
--cc=cdenizet@mozilla.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).