public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97378] [11 Regression] ICE in tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in useless_type_conversion_p, at gimple-expr.c:87 since r11-3685-gfcae5121154d1c33 Date: Mon, 12 Oct 2020 10:17:32 +0000 [thread overview] Message-ID: <bug-97378-4-3vZalIdtAp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97378-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97378 David Binderman <dcb314 at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcb314 at hotmail dot com --- Comment #1 from David Binderman <dcb314 at hotmail dot com> --- I have similar for the following C code: int a, b, c; void d() { e : { long f; long *g = &f; if ((a != 0) - (b = 0)) ; else a &= (*g %= a *= c) >= (*g || f); goto e; } } Compiler flag -O2.
next prev parent reply other threads:[~2020-10-12 10:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 8:08 [Bug tree-optimization/97378] New: [11 Regression] ICE in tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in useless_type_conversion_p, at gimple-expr.c:87 sincer11-3685-gfcae5121154d1c33 marxin at gcc dot gnu.org 2020-10-12 8:09 ` [Bug tree-optimization/97378] " marxin at gcc dot gnu.org 2020-10-12 10:17 ` dcb314 at hotmail dot com [this message] 2020-10-12 11:14 ` [Bug tree-optimization/97378] [11 Regression] ICE in tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in useless_type_conversion_p, at gimple-expr.c:87 since r11-3685-gfcae5121154d1c33 aldyh at gcc dot gnu.org 2020-10-12 11:17 ` rguenth at gcc dot gnu.org 2020-10-12 11:43 ` rguenth at gcc dot gnu.org 2020-10-12 16:53 ` cvs-commit at gcc dot gnu.org 2020-10-12 16:57 ` aldyh at gcc dot gnu.org 2020-10-14 15:36 ` amacleod at redhat dot com
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-97378-4-3vZalIdtAp@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).