public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jbeulich at suse dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94343] [10 Regression] invalid AVX512VL vpternlogd instruction emitted for -march=knl Date: Fri, 27 Mar 2020 09:17:09 +0000 [thread overview] Message-ID: <bug-94343-4-KO9IiCUhB6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94343-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94343 --- Comment #16 from jbeulich at suse dot com --- Oh, right - I didn't pay attention to the insn permitting masking to be used. Then still non-masked uses ought to be permitted, perhaps by having a VI48_AVX512VL one permitting masking and a VI12_AVX512VL one which doesn't?
next prev parent reply other threads:[~2020-03-27 9:17 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-26 15:24 [Bug target/94343] New: " kretz at kde dot org 2020-03-26 15:39 ` [Bug target/94343] " marxin at gcc dot gnu.org 2020-03-26 15:58 ` jakub at gcc dot gnu.org 2020-03-26 16:34 ` hjl.tools at gmail dot com 2020-03-26 16:41 ` jakub at gcc dot gnu.org 2020-03-26 17:08 ` jakub at gcc dot gnu.org 2020-03-26 17:14 ` hjl.tools at gmail dot com 2020-03-26 17:52 ` jakub at gcc dot gnu.org 2020-03-26 17:59 ` jakub at gcc dot gnu.org 2020-03-26 19:30 ` kretz at kde dot org 2020-03-26 19:44 ` jakub at gcc dot gnu.org 2020-03-27 7:00 ` jbeulich at suse dot com 2020-03-27 7:07 ` jbeulich at suse dot com 2020-03-27 7:31 ` jbeulich at suse dot com 2020-03-27 8:45 ` jakub at gcc dot gnu.org 2020-03-27 9:11 ` jakub at gcc dot gnu.org 2020-03-27 9:17 ` jbeulich at suse dot com [this message] 2020-03-27 9:21 ` jakub at gcc dot gnu.org 2020-03-30 16:05 ` cvs-commit at gcc dot gnu.org 2020-03-30 16:06 ` 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-94343-4-KO9IiCUhB6@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).