public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/88873] missing vectorization for decomposed operations on a vector type Date: Wed, 21 Jun 2023 22:18:54 +0000 [thread overview] Message-ID: <bug-88873-4-Nz2QDwDlxK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88873-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88873 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at nextmovesoftware dot com --- Comment #5 from Roger Sayle <roger at nextmovesoftware dot com> --- I have a patch (series) that improves some of the TImode parameter passing issues with the ABI. I'll check/investigate whether this fixes DFmode in the same way that it improves DImode. I worry that the (hi<<64)|lo idiom might not be applicable for FP (without SUBREGs), but something similar (with vec_merge) may resolve this issue during RTL expansion.
next prev parent reply other threads:[~2023-06-21 22:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88873-4@http.gcc.gnu.org/bugzilla/> 2021-08-21 21:25 ` [Bug tree-optimization/88873] " pinskia at gcc dot gnu.org 2023-06-21 13:33 ` [Bug middle-end/88873] " rguenth at gcc dot gnu.org 2023-06-21 22:18 ` roger at nextmovesoftware dot com [this message] 2023-07-10 8:09 ` cvs-commit at gcc dot gnu.org 2023-07-12 11:33 ` rguenth at gcc dot gnu.org 2023-07-14 17:13 ` cvs-commit at gcc dot gnu.org 2023-07-20 8:25 ` cvs-commit at gcc dot gnu.org 2023-08-04 15:24 ` 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-88873-4-Nz2QDwDlxK@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).