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 tree-optimization/97579] [11 Regression] ICE in gimple_expand_vec_cond_expr, at gimple-isel.cc:201 since r11-4123-g128f43cf679e5156 Date: Tue, 03 Nov 2020 15:23:15 +0000 [thread overview] Message-ID: <bug-97579-4-MONbb9Bo9f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97579-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97579 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:d0d8a1658054258baae87b445678c1c0c08d9455 commit r11-4674-gd0d8a1658054258baae87b445678c1c0c08d9455 Author: Richard Biener <rguenther@suse.de> Date: Tue Nov 3 14:53:24 2020 +0100 middle-end/97579 - fix VEC_COND_EXPR ISEL optab query This fixes a mistake in the optab query done by ISEL. It doesn't fix the PR but shifts the ICE elsewhere. 2020-11-03 Richard Biener <rguenther@suse.de> PR middle-end/97579 * gimple-isel.cc (gimple_expand_vec_cond_expr): Use the correct types for the vcond_mask/vec_cmp optab queries.
next prev parent reply other threads:[~2020-11-03 15:23 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-26 11:44 [Bug tree-optimization/97579] New: " marxin at gcc dot gnu.org 2020-10-26 11:44 ` [Bug tree-optimization/97579] " marxin at gcc dot gnu.org 2020-10-26 12:32 ` rguenth at gcc dot gnu.org 2020-10-27 16:09 ` marxin at gcc dot gnu.org 2020-10-28 7:27 ` rguenther at suse dot de 2020-10-29 13:21 ` marxin at gcc dot gnu.org 2020-11-03 15:23 ` cvs-commit at gcc dot gnu.org [this message] 2020-11-18 14:27 ` jakub at gcc dot gnu.org 2020-11-18 14:30 ` jakub at gcc dot gnu.org 2020-11-19 7:21 ` rguenth at gcc dot gnu.org 2020-11-25 11:32 ` rguenth at gcc dot gnu.org 2020-11-25 14:01 ` cvs-commit at gcc dot gnu.org 2020-11-25 14:02 ` rguenth at gcc dot gnu.org 2020-11-30 7:35 ` rguenth 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-97579-4-MONbb9Bo9f@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).