From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, d@dcepelik.cz, ebotcazou@adacore.com
Subject: Re: Remove nonoverlapping_component_refs_of_decl_p
Date: Fri, 14 Jun 2019 20:39:00 -0000 [thread overview]
Message-ID: <20190614203902.ont5hqtrnrcwrzey@kam.mff.cuni.cz> (raw)
In-Reply-To: <20190614201548.rfkpgm3n3ftq5tl3@kam.mff.cuni.cz>
... and forgot to add stats for tramp3d :)
Alias oracle query stats:
refs_may_alias_p: 3021539 disambiguations, 3321136 queries
ref_maybe_used_by_call_p: 7118 disambiguations, 3047133 queries
call_may_clobber_ref_p: 817 disambiguations, 817 queries
nonoverlapping_component_refs_p: 22 disambiguations, 61735 queries
nonoverlapping_component_refs_of_decl_p: 19 disambiguations, 2192 queries
aliasing_component_refs_p: 2050 disambiguations, 19908 queries
TBAA oracle: 1419961 disambiguations 2916692 queries
555158 are in alias set 0
575103 queries asked about the same object
0 queries asked about the same alias set
0 access volatile
252874 are dependent in the DAG
113596 are aritificially in conflict with void *
PTA query stats:
pt_solution_includes: 671982 disambiguations, 952513 queries
pt_solutions_intersect: 97060 disambiguations, 437912 queries
next prev parent reply other threads:[~2019-06-14 20:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 8:49 Jan Hubicka
2019-06-14 10:40 ` Richard Biener
2019-06-14 10:57 ` Jan Hubicka
2019-06-14 11:22 ` Richard Biener
2019-06-14 11:25 ` Jan Hubicka
2019-06-14 12:11 ` Richard Biener
2019-06-14 20:16 ` Jan Hubicka
2019-06-14 20:39 ` Jan Hubicka [this message]
2019-06-16 15:38 ` Jan Hubicka
2019-06-17 6:38 ` Richard Biener
2019-06-17 7:02 ` Jan Hubicka
2019-06-17 7:52 ` Richard Biener
2019-06-17 8:01 ` Jan Hubicka
2019-06-17 10:23 ` Jan Hubicka
2019-06-17 12:46 ` Jan Hubicka
2019-06-17 13:41 ` Richard Biener
2019-06-17 13:51 ` Jan Hubicka
2019-06-22 15:36 ` Jan Hubicka
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=20190614203902.ont5hqtrnrcwrzey@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=d@dcepelik.cz \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).