public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97737] [11 Regression] ICE at -Os and above: tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in useless_type_conversion_p, at gimple-expr.c:88 Date: Fri, 06 Nov 2020 19:30:04 +0000 [thread overview] Message-ID: <bug-97737-4-su55PNzqO1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97737 Andrew Macleod <amacleod at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |FIXED --- Comment #6 from Andrew Macleod <amacleod at redhat dot com> --- I also put this testcase into the suite since propagating undefined in range-ops would also fix the Other PR, but not this one. So although the problem are similar and covered by the same patch, its possible to change the fix for one and not fix the other. Still, fixed.
prev parent reply other threads:[~2020-11-06 19:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-06 5:52 [Bug tree-optimization/97737] New: " zhendong.su at inf dot ethz.ch 2020-11-06 7:26 ` [Bug tree-optimization/97737] [11 Regression] " rguenth at gcc dot gnu.org 2020-11-06 9:50 ` marxin at gcc dot gnu.org 2020-11-06 16:09 ` amacleod at redhat dot com 2020-11-06 16:31 ` zhendong.su at inf dot ethz.ch 2020-11-06 19:27 ` cvs-commit at gcc dot gnu.org 2020-11-06 19:30 ` amacleod at redhat dot com [this message]
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-97737-4-su55PNzqO1@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).