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/111622] New: [13 Regression] EVRP compile-time hog compiling risc-v insn-opinit.cc Date: Thu, 28 Sep 2023 08:43:16 +0000 [thread overview] Message-ID: <bug-111622-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111622 Bug ID: 111622 Summary: [13 Regression] EVRP compile-time hog compiling risc-v insn-opinit.cc Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- Compiling insn-opinit.cc with a x86_64 GCC 13.2 host compiler targeting riscv64-linux with -O2 shows tree Early VRP : 97.26 ( 77%) 0.01 ( 1%) 97.28 ( 76%) 2908k ( 0%) TOTAL : 127.13 1.06 128.21 931M and sofar unchanged on the branch head. It's improved with GCC 14 where we instead have the worst passes being alias stmt walking : 5.89 ( 19%) 0.10 ( 10%) 6.01 ( 19%) 8531k ( 1%) tree FRE : 4.73 ( 16%) 0.04 ( 4%) 4.76 ( 15%) 4325k ( 0%) GCC 12 is fine as well.
next reply other threads:[~2023-09-28 8:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-28 8:43 rguenth at gcc dot gnu.org [this message] 2023-09-28 8:44 ` [Bug tree-optimization/111622] " rguenth at gcc dot gnu.org 2023-09-28 8:44 ` rguenth at gcc dot gnu.org 2023-09-28 8:45 ` rguenth at gcc dot gnu.org 2023-09-28 14:58 ` amacleod at redhat dot com 2023-09-29 6:17 ` rguenth at gcc dot gnu.org 2023-09-29 6:20 ` rguenth at gcc dot gnu.org 2023-10-12 16:32 ` amacleod at redhat dot com 2023-10-13 13:23 ` cvs-commit at gcc dot gnu.org 2023-10-13 13:23 ` cvs-commit at gcc dot gnu.org 2023-10-13 13:50 ` amacleod at redhat dot com
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-111622-4@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).