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 c/105151] [12 Regression] ICE in gimple_range_global with invalid "gimple" language Date: Tue, 05 Apr 2022 07:55:25 +0000 [thread overview] Message-ID: <bug-105151-4-9sSQhOyQnS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105151-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105151 --- Comment #3 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:e68f5c90bae44e886bd1b13a135dbfd00bceea0a commit r12-7994-ge68f5c90bae44e886bd1b13a135dbfd00bceea0a Author: Richard Biener <rguenther@suse.de> Date: Tue Apr 5 09:51:32 2022 +0200 c/105151 - move early walloca pass When the walloca pass gained support for ranger the early pass was not moved to a place where SSA form is available but remained in the lowering pipeline. For the testcase in this bug this is a problem because for errorneous input we still run the lowering pipeline but here have broken SSA form which ranger does not like. The solution is to rectify the mistake with using ranger without SSA form and move the pass which solves both issues. 2022-04-05 Richard Biener <rguenther@suse.de> PR c/105151 * passes.def (pass_walloca): Move early instance into pass_build_ssa_passes to make SSA form available. * gcc.dg/gimplefe-error-14.c: New testcase.
next prev parent reply other threads:[~2022-04-05 7:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-04 16:45 [Bug c/105151] New: [12 Regression] ICE in gimple_range_global, at value-query.cc:424 gscfq@t-online.de 2022-04-05 6:59 ` [Bug c/105151] [12 Regression] ICE in gimple_range_global with invalid "gimple" language rguenth at gcc dot gnu.org 2022-04-05 7:16 ` aldyh at gcc dot gnu.org 2022-04-05 7:55 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-05 7:55 ` 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-105151-4-9sSQhOyQnS@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).