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 rtl-optimization/108086] [11 Regression] internal compiler error: in set_accesses, at rtl-ssa/internals.inl:449
Date: Fri, 14 Apr 2023 13:15:48 +0000 [thread overview]
Message-ID: <bug-108086-4-WsRtKlZ9bw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108086-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108086
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #19 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
With trunk I now get:
phase opt and generate : 71.71 (100%) 4.60 ( 95%) 76.32 ( 99%)
2848M ( 98%)
callgraph functions expansion : 27.25 ( 38%) 1.65 ( 34%) 28.90 ( 38%)
510M ( 17%)
callgraph ipa passes : 44.43 ( 62%) 2.95 ( 61%) 47.38 ( 62%)
2333M ( 80%)
integration : 6.99 ( 10%) 1.05 ( 22%) 8.01 ( 10%)
1998M ( 68%)
tree PTA : 36.28 ( 50%) 2.52 ( 52%) 38.80 ( 50%)
45k ( 0%)
combiner : 3.96 ( 5%) 0.00 ( 0%) 3.96 ( 5%)
41M ( 1%)
with over 5% runtime. Perf claims it is mostly bitmap operations:
16.91% cc1plus cc1plus [.] bitmap_ior_into
12.22% cc1plus cc1plus [.] bitmap_set_bit
3.58% cc1plus cc1plus [.] 0x00000000011cad58
1.97% cc1plus cc1plus [.] bitmap_bit_p
1.80% cc1plus cc1plus [.] bitmap_copy
1.24% cc1plus cc1plus [.] htab_find_slot_with_hash
1.13% cc1plus cc1plus [.] 0x00000000011cad70
1.11% cc1plus cc1plus [.] refers_to_regno_p
next prev parent reply other threads:[~2023-04-14 13:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:40 [Bug c++/108086] New: " jonas.keller@uni-bielefeld.de
2022-12-13 18:42 ` [Bug c++/108086] " jonas.keller@uni-bielefeld.de
2022-12-13 18:43 ` jonas.keller@uni-bielefeld.de
2022-12-13 18:43 ` jonas.keller@uni-bielefeld.de
2022-12-14 8:35 ` [Bug rtl-optimization/108086] " rguenth at gcc dot gnu.org
2022-12-14 8:47 ` rguenth at gcc dot gnu.org
2022-12-14 10:53 ` marxin at gcc dot gnu.org
2022-12-15 10:30 ` rguenth at gcc dot gnu.org
2022-12-15 10:32 ` cvs-commit at gcc dot gnu.org
2022-12-15 17:43 ` cvs-commit at gcc dot gnu.org
2022-12-16 8:30 ` cvs-commit at gcc dot gnu.org
2022-12-16 9:29 ` cvs-commit at gcc dot gnu.org
2022-12-16 11:27 ` [Bug rtl-optimization/108086] [11/12/13 Regression] " rguenth at gcc dot gnu.org
2022-12-16 11:32 ` rguenth at gcc dot gnu.org
2022-12-16 12:06 ` cvs-commit at gcc dot gnu.org
2022-12-16 18:21 ` rsandifo at gcc dot gnu.org
2023-02-02 10:41 ` rsandifo at gcc dot gnu.org
2023-02-02 14:53 ` cvs-commit at gcc dot gnu.org
2023-04-03 8:57 ` [Bug rtl-optimization/108086] [11/12 " cvs-commit at gcc dot gnu.org
2023-04-14 13:15 ` hubicka at gcc dot gnu.org [this message]
2023-05-29 10:07 ` [Bug rtl-optimization/108086] [11 " jakub at gcc dot gnu.org
2024-02-19 13:43 ` rguenth at gcc dot gnu.org
2024-06-04 12:48 ` cvs-commit at gcc dot gnu.org
2024-06-04 12:50 ` rsandifo 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-108086-4-WsRtKlZ9bw@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).