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/108426] [13 regression] SEGV in contains_struct_check Date: Mon, 16 Jan 2023 22:02:35 +0000 [thread overview] Message-ID: <bug-108426-4-Z0700GLeum@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108426-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108426 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Simple fix until we figure out if the go front-end should be initializing these builtins are not: diff --git a/gcc/tree-ssa-loop-niter.cc b/gcc/tree-ssa-loop-niter.cc index 65b960461ae..0a0873bb572 100644 --- a/gcc/tree-ssa-loop-niter.cc +++ b/gcc/tree-ssa-loop-niter.cc @@ -2246,6 +2246,9 @@ build_cltz_expr (tree src, bool leading, bool define_at_zero) else return NULL_TREE; + if (!use_ifn && !fn) + return NULL_TREE; + tree call; if (use_ifn) {
next prev parent reply other threads:[~2023-01-16 22:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-16 21:56 [Bug tree-optimization/108426] New: " ro at gcc dot gnu.org 2023-01-16 21:57 ` [Bug tree-optimization/108426] " ro at gcc dot gnu.org 2023-01-16 22:02 ` pinskia at gcc dot gnu.org [this message] 2023-01-16 22:06 ` [Bug go/108426] " pinskia at gcc dot gnu.org 2023-01-16 22:07 ` pinskia at gcc dot gnu.org 2023-01-17 2:49 ` ian at airs dot com 2023-01-17 7:08 ` rguenth at gcc dot gnu.org 2023-01-17 8:16 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-01-17 17:05 ` cvs-commit at gcc dot gnu.org 2023-01-17 17:06 ` ian at airs dot com 2023-01-17 17:06 ` ian at airs dot com 2023-01-17 17:11 ` pinskia 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-108426-4-Z0700GLeum@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).