public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/99105] [11 regression] profile streaming scales poorly to projects with many source files
Date: Mon, 15 Feb 2021 20:20:20 +0000 [thread overview]
Message-ID: <bug-99105-4-UX1GoAFobk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99105-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99105
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|profile streaming scales |[11 regression] profile
|poorly to projects with |streaming scales poorly to
|many source files |projects with many source
| |files
--- Comment #14 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
With GCC10 the testuiste seems to run reasonably fast (in about 20 minutes
too). Profile is
21.38% clang-11 [.] gcov_do_dump
9.99% clang-11 [.] gcov_read_words
5.42% [kernel] [k]
copy_user_enhanced_fast_string
2.68% FileCheck [.] lstep
2.63% [kernel] [k] clear_page_erms
2.53% clang-11 [.] __gcov_merge_add
2.23% clang-11 [.] gcov_write_words
1.93% clang-11 [.]
__gcov_read_counter
1.50% clang-11 [.]
__gcov_merge_topn
1.29% [kernel] [k]
native_queued_spin_lock_slowpath
1.26% [kernel] [k] alloc_set_pte
1.20% [kernel] [k]
__x86_indirect_thunk_rax
1.05% FileCheck [.] sstep
0.79% [kernel] [k] _raw_spin_lock
0.78% [kernel] [k] kmem_cache_free
0.78% [kernel] [k]
generic_file_buffered_read
0.72% [kernel] [k] kmem_cache_alloc
0.69% [kernel] [k] kfree
0.64% [kernel] [k] page_remove_rmap
0.63% [kernel] [k]
filemap_map_pages
0.60% [kernel] [k] __slab_free
0.55% [kernel] [k] handle_mm_fault
So I am marking this a regression at least until we analyze it better.
next prev parent reply other threads:[~2021-02-15 20:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 13:46 [Bug gcov-profile/99105] New: " hubicka at gcc dot gnu.org
2021-02-15 13:56 ` [Bug gcov-profile/99105] " hubicka at gcc dot gnu.org
2021-02-15 13:58 ` marxin at gcc dot gnu.org
2021-02-15 14:19 ` Jan Hubicka
2021-02-15 13:59 ` marxin at gcc dot gnu.org
2021-02-15 14:19 ` hubicka at ucw dot cz
2021-02-15 14:38 ` marxin at gcc dot gnu.org
2021-02-15 14:50 ` hubicka at ucw dot cz
2021-02-15 14:56 ` marxin at gcc dot gnu.org
2021-02-15 15:17 ` hubicka at ucw dot cz
2021-02-15 15:18 ` marxin at gcc dot gnu.org
2021-02-15 15:21 ` Jan Hubicka
2021-02-15 15:21 ` hubicka at ucw dot cz
2021-02-15 15:21 ` marxin at gcc dot gnu.org
2021-02-15 15:23 ` marxin at gcc dot gnu.org
2021-02-15 15:32 ` Jan Hubicka
2021-02-15 15:32 ` hubicka at ucw dot cz
2021-02-15 16:12 ` hubicka at ucw dot cz
2021-02-15 20:20 ` hubicka at gcc dot gnu.org [this message]
2021-02-15 20:40 ` [Bug gcov-profile/99105] [11 regression] " hubicka at gcc dot gnu.org
2021-02-16 10:31 ` marxin at gcc dot gnu.org
2021-02-16 13:57 ` marxin at gcc dot gnu.org
2021-03-04 15:22 ` cvs-commit at gcc dot gnu.org
2021-03-04 15:23 ` marxin at gcc dot gnu.org
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=bug-99105-4-UX1GoAFobk@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).