public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105463] [11/12/13 Regression] MVE: Wrong code, incorrect alignment assumption Date: Tue, 03 May 2022 16:19:33 +0000 [thread overview] Message-ID: <bug-105463-4-y4lo6h6h14@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105463-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105463 --- Comment #5 from Alex Coplan <acoplan at gcc dot gnu.org> --- FWIW (which is probably not much) with -O3 the problem started with r11-3681-g29c650cd899496c4f9bc069d03d0d7ecfb632176 . commit 29c650cd899496c4f9bc069d03d0d7ecfb632176 Author: Dennis Zhang <dennis.zh@live.com> Date: Tue Oct 6 16:53:46 2020 arm: Enable MVE SIMD modes for vectorization But I suppose the underlying issue is likely still latent (to do with the movmisalign pattern as richi mentioned above).
next prev parent reply other threads:[~2022-05-03 16:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-03 9:52 [Bug target/105463] New: [12/13 " acoplan at gcc dot gnu.org 2022-05-03 11:31 ` [Bug target/105463] " rguenth at gcc dot gnu.org 2022-05-03 11:34 ` rguenth at gcc dot gnu.org 2022-05-03 13:29 ` acoplan at gcc dot gnu.org 2022-05-03 13:42 ` [Bug target/105463] [11/12/13 " rguenth at gcc dot gnu.org 2022-05-03 14:59 ` rearnsha at gcc dot gnu.org 2022-05-03 16:19 ` acoplan at gcc dot gnu.org [this message] 2022-05-13 10:25 ` cvs-commit at gcc dot gnu.org 2022-05-13 10:31 ` [Bug target/105463] [11/12 " rearnsha at gcc dot gnu.org 2022-07-26 11:34 ` rguenth at gcc dot gnu.org 2022-09-02 10:16 ` cvs-commit at gcc dot gnu.org 2022-09-02 11:20 ` [Bug target/105463] [11 " cvs-commit at gcc dot gnu.org 2022-09-02 11:21 ` rearnsha 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-105463-4-y4lo6h6h14@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).