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 ipa/92535] [10/11 regression] ICF is relatively expensive and became less effective
Date: Wed, 18 Nov 2020 08:26:56 +0000 [thread overview]
Message-ID: <bug-92535-4-axE70oAiu1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92535-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92535
--- Comment #13 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Actually, I did not wait long enough for ICF to finish dumping. Here is the
correct output. Still nice improvement for OBJ_TYPE_REF
8399 false returned: 'parameter type is not compatible' in
compatible_parm_types_p at ../../gcc/ipa-icf.c:512
10187 false returned: 'inline attributes are different' in
compare_referenced_symbol_properties at ../../gcc/ipa-icf.c:350
16217 false returned: 'parameter types are not compatible' in equals_wpa at
../../gcc/ipa-icf.c:639
26071 false returned: 'references to virtual tables cannot be merged' in
compare_referenced_symbol_properties at ../../gcc/ipa-icf.c:373
28812 false returned: 'decl_or_type flags are different' in equals_wpa at
../../gcc/ipa-icf.c:572
32287 false returned: 'different tree types' in compatible_types_p at
../../gcc/ipa-icf-gimple.c:206
60520 false returned: 'call function types are not compatible' in
compare_gimple_call at ../../gcc/ipa-icf-gimple.c:635
103684 false returned: 'types are not compatible' in compatible_types_p at
../../gcc/ipa-icf-gimple.c:212
119994 false returned: 'result types are different' in equals_wpa at
../../gcc/ipa-icf.c:621
134888 false returned: '' in compare_gimple_call at
../../gcc/ipa-icf-gimple.c:607
264624 false returned: 'compare_ao_refs failed (semantic difference)' in
compare_operand at ../../gcc/ipa-icf-gimple.c:336
456907 false returned: 'THIS pointer ODR type mismatch' in equals_wpa at
../../gcc/ipa-icf.c:677
460246 false returned: 'types are not same for ODR' in
compatible_polymorphic_types_p at ../../gcc/ipa-icf-gimple.c:197
881974 false returned: 'operand_equal_p failed' in compare_operand at
../../gcc/ipa-icf-gimple.c:356
1011296 false returned: 'GIMPLE assignment operands are different' in
compare_gimple_assign at ../../gcc/ipa-icf-gimple.c:699
1239444 false returned: '' in equals_private at ../../gcc/ipa-icf.c:886
next prev parent reply other threads:[~2020-11-18 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92535-4@http.gcc.gnu.org/bugzilla/>
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2020-11-17 19:49 ` hubicka at gcc dot gnu.org
2020-11-17 20:03 ` hubicka at gcc dot gnu.org
2020-11-17 20:05 ` hubicka at gcc dot gnu.org
2020-11-17 20:21 ` hubicka at gcc dot gnu.org
2020-11-17 21:37 ` hubicka at gcc dot gnu.org
2020-11-18 7:33 ` hubicka at gcc dot gnu.org
2020-11-18 8:26 ` hubicka at gcc dot gnu.org [this message]
2020-11-19 13:57 ` hubicka at gcc dot gnu.org
2020-11-19 18:10 ` hubicka at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-04-15 9:38 ` [Bug ipa/92535] [10 " hubicka at gcc dot gnu.org
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2022-06-28 10:38 ` jakub at gcc dot gnu.org
2023-07-07 8:41 ` 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-92535-4-axE70oAiu1@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).