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/103596] [9/10/11 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.c:88 since r8-565-g7581ce9a1ad6df9c
Date: Fri, 28 Jan 2022 14:16:36 +0000	[thread overview]
Message-ID: <bug-103596-4-UQLl85WfPF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103596-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103596

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:08f594465fa9b6a4ea1e3816cfecf256e883ff53

commit r11-9524-g08f594465fa9b6a4ea1e3816cfecf256e883ff53
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Dec 7 11:13:39 2021 +0100

    tree-optimization/103596 - fix missed propagation into switches

    may_propagate_copy unnecessarily restricts propagating non-abnormals
    into places that currently contain an abnormal SSA name but are
    not the PHI argument for an abnormal edge.  This causes VN to
    not elide a CFG path that it assumes is elided, resulting in
    released SSA names in the IL.

    The fix is to enhance the may_propagate_copy API to specify the
    destination is _not_ a PHI argument.  I chose to not update only
    the relevant caller in VN and the may_propagate_copy_into_stmt API
    at this point because this is a regression and needs backporting.

    2021-12-07  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/103596
            * tree-ssa-sccvn.c (eliminate_dom_walker::eliminate_stmt):
            Note we are not propagating into a PHI argument to
may_propagate_copy.
            * tree-ssa-propagate.h (may_propagate_copy): Add
            argument specifying whether we propagate into a PHI arg.
            * tree-ssa-propagate.c (may_propagate_copy): Likewise.
            When not doing so we can replace an abnormal with
            something else.
            (may_propagate_into_stmt): Update may_propagate_copy calls.
            (replace_exp_1): Move propagation checking code to
            propagate_value and rename to ...
            (replace_exp): ... this and elide previous wrapper.
            (propagate_value): Perform checking with adjusted
            may_propagate_copy call and dispatch to replace_exp.

            * gcc.dg/torture/pr103596.c: New testcase.

    (cherry picked from commit 6e8a31275fda445fb3e8d98e53f5e1541f4727af)

  parent reply	other threads:[~2022-01-28 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  6:04 [Bug tree-optimization/103596] New: [11/12 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.c:88 asolokha at gmx dot com
2021-12-07  6:14 ` [Bug tree-optimization/103596] [9/10/11/12 " pinskia at gcc dot gnu.org
2021-12-07  6:18 ` pinskia at gcc dot gnu.org
2021-12-07  8:26 ` [Bug tree-optimization/103596] [9/10/11/12 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.c:88 since r8-565-g7581ce9a1ad6df9c marxin at gcc dot gnu.org
2021-12-07  9:46 ` rguenth at gcc dot gnu.org
2021-12-07 10:12 ` rguenth at gcc dot gnu.org
2021-12-07 13:09 ` cvs-commit at gcc dot gnu.org
2022-01-28 14:16 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-21 12:52 ` [Bug tree-optimization/103596] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-27  9:51 ` [Bug tree-optimization/103596] [9 " 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-103596-4-UQLl85WfPF@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: link
Be 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).