public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/98932] Wrong output with -O3 on aarch64 Date: Tue, 02 Feb 2021 18:42:47 +0000 [thread overview] Message-ID: <bug-98932-4-GUZrM11ugq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98932-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98932 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |11.0 CC| |rguenth at gcc dot gnu.org, | |rsandifo at gcc dot gnu.org Status|ASSIGNED |NEW Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot gnu.org --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> --- Ok, so the issue was fixed in g:74166aabeb7f22990476b1169bba031b8323ee92, which is about a preferred vector types. So with the following patch: diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c index 9e88438b3c3..1e5a05a00b0 100644 --- a/gcc/config/aarch64/aarch64.c +++ b/gcc/config/aarch64/aarch64.c @@ -17351,14 +17351,14 @@ aarch64_autovectorize_vector_modes (vector_modes *modes, bool) TODO: We could support a limited form of V4QImode too, so that we use 32-bit vectors for 8-bit elements. */ - V4HImode, +// V4HImode, /* Try using 64-bit vectors for 32-bit elements and 128-bit vectors for 64-bit elements. TODO: We could similarly support limited forms of V2QImode and V2HImode for this case. */ - V2SImode +// V2SImode }; /* Try using N-byte SVE modes only after trying N-byte Advanced SIMD mode. @@ -23901,8 +23901,8 @@ aarch64_libgcc_floating_mode_supported_p #define TARGET_VECTORIZE_VEC_PERM_CONST \ aarch64_vectorize_vec_perm_const -#undef TARGET_VECTORIZE_RELATED_MODE -#define TARGET_VECTORIZE_RELATED_MODE aarch64_vectorize_related_mode +//#undef TARGET_VECTORIZE_RELATED_MODE +//#define TARGET_VECTORIZE_RELATED_MODE aarch64_vectorize_related_mode #undef TARGET_VECTORIZE_GET_MASK_MODE #define TARGET_VECTORIZE_GET_MASK_MODE aarch64_get_mask_mode #undef TARGET_VECTORIZE_EMPTY_MASK_IS_EXPENSIVE I tracked that it was fixed with g:04b99da898a9817e72fedb4063589648b7961ac5, which is a vectorizer related revision. Thus it's likely dup of PR97236. Can we backport the fixed into 8 and 9 branch?
next prev parent reply other threads:[~2021-02-02 18:42 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 13:20 [Bug c++/98932] New: " kristian.klausen at scoutdi dot com 2021-02-02 13:21 ` [Bug c++/98932] " kristian.klausen at scoutdi dot com 2021-02-02 13:24 ` marxin at gcc dot gnu.org 2021-02-02 18:42 ` marxin at gcc dot gnu.org [this message] 2021-02-03 8:25 ` [Bug tree-optimization/98932] " rguenth at gcc dot gnu.org 2021-02-05 11:15 ` kristian.klausen at scoutdi dot com 2021-02-05 11:36 ` marxin at gcc dot gnu.org 2021-02-05 11:45 ` kristian.klausen at scoutdi dot com
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-98932-4-GUZrM11ugq@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).