public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chengcongxiu at huawei dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/95668] New: patching the commit of SVE on GCC7.3, But fail in test Date: Sun, 14 Jun 2020 07:18:40 +0000 [thread overview] Message-ID: <bug-95668-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95668 Bug ID: 95668 Summary: patching the commit of SVE on GCC7.3, But fail in test Product: gcc Version: 7.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: chengcongxiu at huawei dot com Target Milestone: --- Created attachment 48727 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48727&action=edit The gcc as follow: The test as follow: void foo (int * restrict in, int * restrict out, int s) { for (int i = 0; i < 16; i++) { for (int j = 0; j < 6; ++j) out[j] = in[j]; in += 6; out += s*6; } } using gcc compile above test: .cfi_startproc movi v5.2s, 0 add w2, w2, w2, lsl 1 ldr q16, [x0] lsl w2, w2, 1 ldr q7, [x0, 16] sbfiz x2, x2, 2, 32 orr v4.8b, v5.8b, v5.8b orr v3.8b, v5.8b, v5.8b orr v2.8b, v5.8b, v5.8b orr v1.8b, v5.8b, v5.8b ldr q6, [x0, 32] orr v0.8b, v5.8b, v5.8b orr v25.8b, v5.8b, v5.8b orr v24.8b, v5.8b, v5.8b ins v4.s[60], v16.s[61] //this instruction error: ins v5.s[60], v16.s[63] ins v3.s[60], v7.s[63] ins v2.s[60], v7.s[61] ins v1.s[60], v6.s[63] add x5, x1, x2
next reply other threads:[~2020-06-14 7:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-14 7:18 chengcongxiu at huawei dot com [this message] 2020-06-14 7:19 ` [Bug c/95668] " chengcongxiu at huawei dot com 2020-06-14 7:50 ` [Bug target/95668] " pinskia at gcc dot gnu.org 2020-06-15 1:19 ` chengcongxiu at huawei dot com 2020-06-15 1:21 ` 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-95668-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).