public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97717] compilation with -O(1/2/3) flag failed while -O0 succeeds Date: Sun, 26 Dec 2021 06:14:20 +0000 [thread overview] Message-ID: <bug-97717-4-BV9Fu73qJd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97717-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97717 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW Keywords| |compile-time-hog --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- for me, -O1 takes a long time even: callgraph ipa passes : 2.34 ( 26%) 0.49 ( 30%) 2.84 ( 26%) 159M ( 37%) -O2 is much worse: alias stmt walking : 23.12 ( 37%) 0.14 ( 7%) 23.24 ( 36%) 323M ( 17%) tree DSE : 11.34 ( 18%) 0.00 ( 0%) 11.36 ( 18%) 15k ( 0%) tree slp vectorization : 16.01 ( 26%) 0.30 ( 15%) 16.32 ( 25%) 1117M ( 60%) This is with --enable-checking=yes but with -fno-checking. So there is at least a compile time hog here.
next prev parent reply other threads:[~2021-12-26 6:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-04 17:06 [Bug tree-optimization/97717] New: " kranti.rkiran at gmail dot com 2020-11-04 17:12 ` [Bug tree-optimization/97717] " kranti.rkiran at gmail dot com 2020-11-05 7:38 ` rguenth at gcc dot gnu.org 2020-11-17 10:20 ` kranti.rkiran at gmail dot com 2021-12-26 6:14 ` pinskia at gcc dot gnu.org [this message] 2021-12-26 6:18 ` [Bug middle-end/97717] " pinskia at gcc dot gnu.org 2021-12-26 6:27 ` pinskia at gcc dot gnu.org 2021-12-26 6:37 ` pinskia 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-97717-4-BV9Fu73qJd@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).