public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115464] ICE when building libaom on arm64 (neon sve bridge usage with tbl/perm) Date: Wed, 12 Jun 2024 17:44:57 +0000 [thread overview] Message-ID: <bug-115464-4-pTqO3VUSNh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115464-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115464 Tamar Christina <tnfchris at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-06-12 CC| |tnfchris at gcc dot gnu.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Tamar Christina <tnfchris at gcc dot gnu.org> --- Confirmed, slightly more cleaned up example: #include <arm_neon.h> #include <arm_sve.h> #include <arm_neon_sve_bridge.h> int16x8_t convolve4_4_x (uint16x8x2_t permute_tbl, svint16_t res) { return svget_neonq_s16 ( svtbl_s16 (res, svset_neonq_u16 (svundef_u16 (), permute_tbl.val[0]))); }
next prev parent reply other threads:[~2024-06-12 17:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-12 15:50 [Bug target/115464] New: ICE when building libaom on arm64 sjames at gcc dot gnu.org 2024-06-12 15:50 ` [Bug target/115464] " sjames at gcc dot gnu.org 2024-06-12 15:50 ` sjames at gcc dot gnu.org 2024-06-12 17:44 ` tnfchris at gcc dot gnu.org [this message] 2024-06-12 19:04 ` [Bug target/115464] ICE when building libaom on arm64 (neon sve bridge usage with tbl/perm) tnfchris at gcc dot gnu.org 2024-06-12 20:05 ` rsandifo at gcc dot gnu.org 2024-06-13 3:17 ` tnfchris at gcc dot gnu.org 2024-06-13 3:21 ` tnfchris at gcc dot gnu.org 2024-06-13 11:48 ` cvs-commit at gcc dot gnu.org 2024-06-13 11:50 ` [Bug target/115464] [14 Backport] " rsandifo at gcc dot gnu.org 2024-06-13 17:24 ` tnfchris at gcc dot gnu.org 2024-06-14 6:45 ` rsandifo at gcc dot gnu.org 2024-06-18 11:23 ` 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-115464-4-pTqO3VUSNh@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).