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 tree-optimization/109491] [11/12 Regression] Segfault in tree-ssa-sccvn.cc:expressions_equal_p() Date: Fri, 14 Apr 2023 13:32:19 +0000 [thread overview] Message-ID: <bug-109491-4-rRVq3I6DjJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109491-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109491 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #17 from Jan Hubicka <hubicka at gcc dot gnu.org> --- With a cross on znver3 machine I get with ./xgcc -B ./ -mcpu=power8 -std=c++14 -O2 tt.cc --verbose -Q : phase opt and generate : 13.19 ( 99%) 0.35 ( 95%) 13.53 ( 99%) 408M ( 94%) callgraph functions expansion : 10.19 ( 77%) 0.15 ( 41%) 10.33 ( 76%) 193M ( 45%) callgraph ipa passes : 2.97 ( 22%) 0.20 ( 54%) 3.17 ( 23%) 203M ( 47%) df live regs : 0.65 ( 5%) 0.00 ( 0%) 0.62 ( 5%) 0 ( 0%) alias stmt walking : 1.19 ( 9%) 0.03 ( 8%) 1.25 ( 9%) 6915k ( 2%) tree Early VRP : 0.63 ( 5%) 0.01 ( 3%) 0.58 ( 4%) 16M ( 4%) PRE : 2.81 ( 21%) 0.01 ( 3%) 2.83 ( 21%) 349k ( 0%) scheduling : 1.00 ( 8%) 0.00 ( 0%) 0.99 ( 7%) 1997k ( 0%) inliner is: ipa inlining heuristics : 0.49 ( 4%) 0.00 ( 0%) 0.47 ( 3%) 4429k ( 1%) integration : 0.19 ( 1%) 0.04 ( 11%) 0.28 ( 2%) 117M ( 27%) So inlining itself seems to be in control. With RTL SSA we may be able to replace RTL PRE with GVN-PRE :)
next prev parent reply other threads:[~2023-04-14 13:32 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 20:25 [Bug tree-optimization/109491] New: " pthaugen at gcc dot gnu.org 2023-04-12 20:26 ` [Bug tree-optimization/109491] [13 Regression] " pinskia at gcc dot gnu.org 2023-04-12 20:46 ` pthaugen at gcc dot gnu.org 2023-04-12 20:52 ` pinskia at gcc dot gnu.org 2023-04-12 20:54 ` pinskia at gcc dot gnu.org 2023-04-12 21:08 ` bergner at gcc dot gnu.org 2023-04-12 21:16 ` pthaugen at gcc dot gnu.org 2023-04-13 11:34 ` rguenth at gcc dot gnu.org 2023-04-13 11:35 ` rguenth at gcc dot gnu.org 2023-04-13 12:07 ` rguenth at gcc dot gnu.org 2023-04-13 12:17 ` rguenth at gcc dot gnu.org 2023-04-13 13:00 ` cvs-commit at gcc dot gnu.org 2023-04-13 13:01 ` [Bug tree-optimization/109491] [11/12 " rguenth at gcc dot gnu.org 2023-04-13 16:22 ` chip.kerchner at ibm dot com 2023-04-14 7:17 ` rguenth at gcc dot gnu.org 2023-04-14 12:24 ` chip.kerchner at ibm dot com 2023-04-14 12:45 ` rguenther at suse dot de 2023-04-14 13:15 ` rguenth at gcc dot gnu.org 2023-04-14 13:32 ` hubicka at gcc dot gnu.org [this message] 2023-04-17 9:14 ` cvs-commit at gcc dot gnu.org 2023-04-17 10:44 ` [Bug tree-optimization/109491] [11 " cvs-commit at gcc dot gnu.org 2023-04-17 10:46 ` 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-109491-4-rRVq3I6DjJ@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: linkBe 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).