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 target/113869] New: V4HF->V4SF pattern seems to be missing Date: Sun, 11 Feb 2024 01:31:18 +0000 [thread overview] Message-ID: <bug-113869-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113869 Bug ID: 113869 Summary: V4HF->V4SF pattern seems to be missing Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Target: aarch64 Take: ``` void f( _Float16 * __restrict a, float * __restrict b) { b[0] = a[0]; b[1] = a[1]; b[2] = a[2]; b[3] = a[3]; b+=4;a+=4; #if 0 b[0] = a[0]; b[1] = a[1]; b[2] = a[2]; b[3] = a[3]; #endif } ``` The pattern that converts V4HF to V4SF seems be to missing and we don't SLP the above. We able to handle V8HF to V8SF which does: ``` fcvtl v30.4s, v31.4h fcvtl2 v31.4s, v31.8h ``` But the first fcvtl is exactly what we want for V4HF->V4SF.
next reply other threads:[~2024-02-11 1:31 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-11 1:31 pinskia at gcc dot gnu.org [this message] 2024-06-06 18:51 ` [Bug target/113869] " cvs-commit at gcc dot gnu.org 2024-06-11 17:03 ` 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-113869-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).