public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109539] [13/14 Regression] Compile-time hog in gimple-ssa-warn-access.cc since r13-6706-gadb70c2d1060b3
Date: Tue, 18 Apr 2023 09:12:19 +0000 [thread overview]
Message-ID: <bug-109539-4-6HClbWmSFE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109539-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109539
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is almost certainly the cost of pointers_related_p
Samples: 3M of event 'cycles', Event count (approx.): 3573086788171
Children Self Samples Command Shared Object Symbol
- 93.15% 0.80% 25898 cc1plus cc1plus [.] (anonymous
namespace)::pointers_related_p #
- 92.35% (anonymous namespace)::pointers_related_p
#
- 92.30% (anonymous namespace)::pointers_related_p
#
- 92.21% (anonymous namespace)::pointers_related_p
#
- 92.12% (anonymous namespace)::pointers_related_p
#
- 92.02% (anonymous namespace)::pointers_related_p
#
- 91.93% (anonymous namespace)::pointers_related_p
#
- 91.84% (anonymous namespace)::pointers_related_p
#
- 91.75% (anonymous namespace)::pointers_related_p
#
- 91.66% (anonymous namespace)::pointers_related_p
#
- 91.57% (anonymous
namespace)::pointers_related_p #
- 91.48% (anonymous
namespace)::pointers_related_p #
- 91.39% (anonymous
namespace)::pointers_related_p #
- 87.34% (anonymous
namespace)::pointers_related_p #
- 62.30% (anonymous
namespace)::pointers_related_p #
- 44.52% pointer_query::get_ref
#
- 44.51% compute_objsize
#
+ 15.03%
access_ref::size_remaining #
+ 14.49% wide_int_to_tree
#
+ 4.91%
generic_wide_int<fixed_wide_int_storage<128> >::operat#
+ 4.57% operator<
<generic_wide_int<fixed_wide_int_storage<128#
+ 2.41% poly_int<1u,
generic_wide_int<wide_int_ref_storage<fal#
+ 1.15%
pointer_query::~pointer_query #
0.80%
pointer_query::pointer_query #
0.78% compute_objsize_r
#
- 14.08% (anonymous
namespace)::pointers_related_p #
+ 6.14% access_ref::access_ref
#
+ 4.53% pointer_query::get_ref
#
+ 2.07% ptr_derefs_may_alias_p
#
+ 3.70% access_ref::access_ref
#
+ 25.03% pointer_query::get_ref
#
+ 4.04% pointer_query::get_ref
next prev parent reply other threads:[~2023-04-18 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 6:48 [Bug tree-optimization/109539] New: " marxin at gcc dot gnu.org
2023-04-18 6:50 ` [Bug tree-optimization/109539] " marxin at gcc dot gnu.org
2023-04-18 8:22 ` marxin at gcc dot gnu.org
2023-04-18 8:44 ` rguenth at gcc dot gnu.org
2023-04-18 9:12 ` rguenth at gcc dot gnu.org [this message]
2023-04-18 9:49 ` rguenth at gcc dot gnu.org
2023-04-18 12:38 ` cvs-commit at gcc dot gnu.org
2023-04-18 12:38 ` cvs-commit at gcc dot gnu.org
2023-04-18 12:39 ` rguenth 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-109539-4-6HClbWmSFE@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).