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/107009] [13 Regression] massive unnecessary code blowup in vectorizer Date: Fri, 23 Sep 2022 06:43:53 +0000 [thread overview] Message-ID: <bug-107009-4-hsNpJBNvxu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107009 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Priority|P3 |P1 CC| |rguenth at gcc dot gnu.org --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- # RANGE [irange] size_t [1, +INF] size_t n_12(D) = n; the nonzero bits info on 'n' is gone. DOM2 used to produce that and CCP3 elides the __builtin_unreachable () but if DOM2 is disabled that doesn't produce the nonzero bits. DOM2 from trunk no longer sets nonzero bits. CCP doesn't do any conditional non-zero bits (or constant equivalence) propagation.
next prev parent reply other threads:[~2022-09-23 6:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-22 18:49 [Bug tree-optimization/107009] New: " drepper.fsp+rhbz at gmail dot com 2022-09-22 19:00 ` [Bug tree-optimization/107009] [13 Regression] " mpolacek at gcc dot gnu.org 2022-09-22 20:03 ` aldyh at gcc dot gnu.org 2022-09-23 6:43 ` rguenth at gcc dot gnu.org [this message] 2022-09-23 13:57 ` aldyh at gcc dot gnu.org 2022-09-23 17:56 ` aldyh at gcc dot gnu.org 2022-09-23 17:57 ` aldyh at gcc dot gnu.org 2022-09-23 17:57 ` aldyh at gcc dot gnu.org 2022-09-26 14:42 ` cvs-commit at gcc dot gnu.org 2022-09-26 14:43 ` aldyh at gcc dot gnu.org 2022-09-26 17:25 ` cvs-commit 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-107009-4-hsNpJBNvxu@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).