public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97028] [9/10/11 Regression] Compilation errors for AVX512 intrinsic with -masm=intel Date: Tue, 15 Sep 2020 08:29:17 +0000 [thread overview] Message-ID: <bug-97028-4-URddwnDYNn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97028-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97028 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:d0a094ce39fc49681b0d5cfd2ee1d232859c4824 commit r9-8871-gd0a094ce39fc49681b0d5cfd2ee1d232859c4824 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Sep 15 09:37:48 2020 +0200 i386: Fix up vector mul and div with broadcasts in -masm=intel mode These patterns printed bogus <>s around the {1to16} and similar strings. 2020-09-15 Jakub Jelinek <jakub@redhat.com> PR target/97028 * config/i386/sse.md (mul<mode>3<mask_name>_bcs, <avx512>_div<mode>3<mask_name>_bcst): Use <avx512bcst> instead of <<avx512bcst>>. * gcc.target/i386/avx512f-pr97028.c: Untested fix. (cherry picked from commit 0f079e104a8d1994b6b47169a6b45737615eb2d7)
next prev parent reply other threads:[~2020-09-15 8:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-12 0:38 [Bug target/97028] New: " nikita.shulga at gmail dot com 2020-09-12 0:44 ` [Bug target/97028] " nikita.shulga at gmail dot com 2020-09-14 7:10 ` rguenth at gcc dot gnu.org 2020-09-14 7:25 ` [Bug target/97028] [9/10/11 Regression] " jakub at gcc dot gnu.org 2020-09-14 7:29 ` jakub at gcc dot gnu.org 2020-09-14 7:47 ` jakub at gcc dot gnu.org 2020-09-15 7:40 ` cvs-commit at gcc dot gnu.org 2020-09-15 8:29 ` cvs-commit at gcc dot gnu.org 2020-09-15 8:29 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-15 8:29 ` jakub 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-97028-4-URddwnDYNn@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).