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/97506] [11 Regression] ICE: in extract_insn, at recog.c:2294 (unrecognizable insn) with -mavx512vbmi -mavx512vl Date: Wed, 21 Oct 2020 09:34:41 +0000 [thread overview] Message-ID: <bug-97506-4-iICSsmbSum@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97506-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97506 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:9b5d50b7c6e34267b40bdeb4c145e9132d83762d commit r11-4184-g9b5d50b7c6e34267b40bdeb4c145e9132d83762d Author: liuhongt <hongtao.liu@intel.com> Date: Wed Oct 21 13:05:16 2020 +0800 Simplify trivial VEC_COND_EXPR in expander. gcc/ChangeLog: PR target/97506 * config/i386/i386-expand.c (ix86_expand_sse_movcc): Move op_true to dest directly when op_true equals op_false. gcc/testsuite/ChangeLog: PR target/97506 * gcc.target/i386/pr97506.c: New test.
next prev parent reply other threads:[~2020-10-21 9:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-20 17:52 [Bug target/97506] New: " zsojka at seznam dot cz 2020-10-20 18:45 ` [Bug target/97506] " jakub at gcc dot gnu.org 2020-10-21 4:40 ` crazylht at gmail dot com 2020-10-21 6:09 ` rguenth at gcc dot gnu.org 2020-10-21 7:48 ` jakub at gcc dot gnu.org 2020-10-21 8:14 ` crazylht at gmail dot com 2020-10-21 9:34 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-21 9:37 ` crazylht at gmail dot com 2020-10-21 9:41 ` jakub at gcc dot gnu.org 2020-10-21 9:43 ` cvs-commit at gcc dot gnu.org 2020-11-18 16:49 ` 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-97506-4-iICSsmbSum@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).