public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107956] [12/13 Regression] ICE: SIGSEGV in contains_struct_check (tree.h:3641) with -fsanitize=float-cast-overflow -ftree-slp-vectorize -fexceptions Date: Sun, 04 Dec 2022 19:29:44 +0000 [thread overview] Message-ID: <bug-107956-4-Nprhm0bNxb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107956 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This should fix it: diff --git a/gcc/tree-vect-patterns.cc b/gcc/tree-vect-patterns.cc index f6c34bb3263..d9fdb24ee62 100644 --- a/gcc/tree-vect-patterns.cc +++ b/gcc/tree-vect-patterns.cc @@ -4964,6 +4964,8 @@ vect_recog_mask_conversion_pattern (vec_info *vinfo, else { lhs = gimple_call_lhs (last_stmt); + if (!lhs) + return NULL; vectype1 = get_vectype_for_scalar_type (vinfo, TREE_TYPE (lhs)); } Though I think it has been a latent bug since r9-1741-g2c58d42c3ed599 really.
next prev parent reply other threads:[~2022-12-04 19:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-03 14:20 [Bug tree-optimization/107956] New: " zsojka at seznam dot cz 2022-12-04 19:20 ` [Bug tree-optimization/107956] " pinskia at gcc dot gnu.org 2022-12-04 19:25 ` pinskia at gcc dot gnu.org 2022-12-04 19:29 ` pinskia at gcc dot gnu.org [this message] 2022-12-05 8:08 ` rguenth at gcc dot gnu.org 2022-12-05 8:12 ` cvs-commit at gcc dot gnu.org 2022-12-05 8:14 ` cvs-commit at gcc dot gnu.org 2022-12-05 8:14 ` 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-107956-4-Nprhm0bNxb@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).