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/51492] vectorizer does not support saturated arithmetic patterns Date: Tue, 24 Aug 2021 23:44:48 +0000 [thread overview] Message-ID: <bug-51492-4-ioC7stx8j0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51492-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51492 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2016-01-04 00:00:00 |2021-8-24 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- We do slightly better but not close: movdqa (%rax), %xmm0 addq $16, %rax psubusw %xmm1, %xmm0 paddw %xmm1, %xmm0 paddw %xmm2, %xmm0 movaps %xmm0, -16(%rax) Which is expanded from: vect__1.6_15 = MAX_EXPR <vect_m_6.5_3, { 64, 64, 64, 64, 64, 64, 64, 64 }>; vect__2.7_17 = vect__1.6_15 + { 65472, 65472, 65472, 65472, 65472, 65472, 65472, 65472 }; -mavx2 we get: vpmaxuw (%rax), %ymm2, %ymm0 addq $32, %rax vpaddw %ymm1, %ymm0, %ymm0 vmovdqa %ymm0, -32(%rax) Just note 65472 is -64. This shouldn't be too hard to detect and add and even lower back to MAX_EXPR/PLUS_EXPR if us_minus does not exist.
next prev parent reply other threads:[~2021-08-24 23:44 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-10 1:38 [Bug tree-optimization/51492] New: vectorizer generates unnecessary code drepper.fsp at gmail dot com 2011-12-12 10:25 ` [Bug tree-optimization/51492] vectorizer does not support saturated arithmetic patterns rguenth at gcc dot gnu.org 2012-01-08 18:57 ` drepper.fsp at gmail dot com 2012-07-13 8:39 ` rguenth at gcc dot gnu.org 2021-08-24 23:44 ` pinskia at gcc dot gnu.org [this message] 2021-08-25 3:54 ` pinskia at gcc dot gnu.org 2024-02-01 13:06 ` pan2.li at intel dot com 2024-02-01 13:37 ` juzhe.zhong at rivai dot ai 2024-02-01 13:42 ` juzhe.zhong at rivai dot ai 2024-02-01 14:40 ` juzhe.zhong at rivai dot ai 2024-02-01 14:41 ` juzhe.zhong at rivai dot ai 2024-02-01 15:10 ` tnfchris at gcc dot gnu.org 2024-02-02 1:04 ` pan2.li at intel dot com 2024-02-02 11:11 ` tnfchris at gcc dot gnu.org 2024-02-03 6:57 ` pan2.li at intel dot com 2024-02-06 1:13 ` pan2.li at intel dot com 2024-02-06 22:11 ` tnfchris at gcc dot gnu.org 2024-02-07 0:57 ` pan2.li at intel dot com 2024-05-16 12:09 ` cvs-commit at gcc dot gnu.org 2024-05-16 12:09 ` cvs-commit at gcc dot gnu.org 2024-05-18 2:17 ` 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-51492-4-ioC7stx8j0@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).