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/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:27:29 +0000 [thread overview] Message-ID: <bug-97737-4-TrYpCxcwme@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 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>: https://gcc.gnu.org/g:129e1a8a96d140150705fab30d25afb464eb1d99 commit r11-4795-g129e1a8a96d140150705fab30d25afb464eb1d99 Author: Andrew MacLeod <amacleod@redhat.com> Date: Fri Nov 6 14:14:46 2020 -0500 Combine new calculated ranges with existing range. When a range is recalculated, retain what was previously known as IL changes can produce different results from un-executed code. This also paves the way for external injection of ranges. gcc/ PR tree-optimization/97737 PR tree-optimization/97741 * gimple-range.cc: (gimple_ranger::range_of_stmt): Intersect newly calculated ranges with the existing known global range. gcc/testsuite/ * gcc.dg/pr97737.c: New. * gcc.dg/pr97741.c: New.
next prev parent reply other threads:[~2020-11-06 19:27 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 [this message] 2020-11-06 19:30 ` 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-97737-4-TrYpCxcwme@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).