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/94414] only `--` gives constexpr Date: Tue, 14 Dec 2021 08:54:20 +0000 [thread overview] Message-ID: <bug-94414-4-vynUODJpyL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94414 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-12-14 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Severity|normal |enhancement Component|c++ |tree-optimization --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- To me there looks like an unrolling not happening: <bb 3> [local count: 1014686026]: # __first_35 = PHI <__first_15(4), &MEM <const int[4]> [(void *)&arr + 8B](2)> _14 = MEM[(const int &)__first_35]; if (_14 <= 5) goto <bb 4>; [94.50%] else goto <bb 5>; [5.50%] <bb 4> [local count: 958878296]: __first_15 = __first_35 + 4; if (&MEM <const struct array> [(void *)&arr + 16B] != __first_15) goto <bb 3>; [94.50%] else goto <bb 5>; [5.50%] But from what I can tell it is we unroll the one loop and then we can't unroll this one until much later on. It is really interesting testcase.
prev parent reply other threads:[~2021-12-14 8:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-30 21:58 [Bug c++/94414] New: " dmusiienko at gmail dot com 2020-03-31 7:43 ` [Bug c++/94414] " rguenth at gcc dot gnu.org 2020-03-31 9:09 ` redi at gcc dot gnu.org 2020-03-31 15:02 ` ppalka at gcc dot gnu.org 2021-12-14 8:54 ` pinskia at gcc dot gnu.org [this message]
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-94414-4-vynUODJpyL@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).