public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/98602] New: Failure to optimise vector “x > -100 ? x : -100” to MAX_EXPR Date: Fri, 08 Jan 2021 13:22:29 +0000 [thread overview] Message-ID: <bug-98602-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98602 Bug ID: 98602 Summary: Failure to optimise vector “x > -100 ? x : -100” to MAX_EXPR Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rsandifo at gcc dot gnu.org Target Milestone: --- We don't fold: typedef int v4si __attribute__ ((vector_size(16))); v4si f (v4si x) { return x > -100 ? x : -100; } to a MAX_EXPR, even though we do if -100 is replaced with a nonnegative constant or a variable. This may be related to the remaining part of PR95906.
next reply other threads:[~2021-01-08 13:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-08 13:22 rsandifo at gcc dot gnu.org [this message] 2021-01-08 13:48 ` [Bug tree-optimization/98602] " rguenth at gcc dot gnu.org 2021-01-11 18:04 ` cvs-commit at gcc dot gnu.org 2021-06-29 6:38 ` pinskia at gcc dot gnu.org 2021-06-29 6:43 ` 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-98602-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).