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/112375] New: vget_set_lane_1.c fails Date: Sat, 04 Nov 2023 06:06:06 +0000 [thread overview] Message-ID: <bug-112375-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112375 Bug ID: 112375 Summary: vget_set_lane_1.c fails Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: testsuite-fail Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Target: aarch64-linux-gnu FAIL: gcc.target/aarch64/vget_set_lane_1.c scan-assembler-times ins\\\\tv0.s\\\\[1\\\\], v1.s\\\\[0\\\\] 3 We expected ins here but currently get: zip1 v0.2s, v0.2s, v1.2s 3 times.
next reply other threads:[~2023-11-04 6:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-04 6:06 pinskia at gcc dot gnu.org [this message] 2023-11-04 6:12 ` [Bug target/112375] [14 Regression] " pinskia at gcc dot gnu.org 2023-11-04 6:18 ` pinskia at gcc dot gnu.org 2024-01-16 11:45 ` belagod at gcc dot gnu.org 2024-01-16 11:45 ` belagod at gcc dot gnu.org 2024-02-22 15:32 ` cvs-commit at gcc dot gnu.org 2024-02-24 2:20 ` 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-112375-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).