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/97360] [11 Regression] ICE in range_on_exit
Date: Wed, 21 Oct 2020 19:30:17 +0000 [thread overview]
Message-ID: <bug-97360-4-Cp9VM8diT7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97360-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97360
--- Comment #36 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Peter Bergner <bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:84cc3370d6d5972fe495b2114fb32f7b4a49a98d
commit r11-4193-g84cc3370d6d5972fe495b2114fb32f7b4a49a98d
Author: Richard Biener <rguenther@suse.de>
Date: Wed Oct 21 14:28:45 2020 -0500
rs6000: MMA type causes an ICE in ranger pass due to incompatible types
PR97360 shows a problem in how we create our PXI and POI modes that cause
an ICE in the ranger pass. The problem seems to be that the extra call
to build_distinct_type_copy() also creates new TYPE_{MIN,MAX}_VALUEs that
are not compatible/the same as the base type itself. The simple "fix" is
to actually remove the unneeded build_distinct_type_copy(), since according
to richi, the types returned from make_unsigned_type() are already
distinct.
gcc/
2020-10-21 Richard Biener <rguenther@suse.de>
PR target/97360
* config/rs6000/rs6000-call.c (rs6000_init_builtins): Remove call
to
build_distinct_type_copy().
gcc/testsuite/
2020-10-21 Martin Liska <mliska@suse.cz>
PR target/97360
* gcc.target/powerpc/pr97360.c: New test.
Co-authored-by: Andrew MacLeod <amacleod@redhat.com>
Co-authored-by: Martin Liska <mliska@suse.cz>
next prev parent reply other threads:[~2020-10-21 19:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 3:08 [Bug tree-optimization/97360] New: " amodra at gmail dot com
2020-10-11 22:07 ` [Bug tree-optimization/97360] " msebor at gcc dot gnu.org
2020-10-12 6:23 ` [Bug tree-optimization/97360] [11 Regression] " rguenth at gcc dot gnu.org
2020-10-12 7:42 ` marxin at gcc dot gnu.org
2020-10-12 8:02 ` amodra at gmail dot com
2020-10-12 8:06 ` amodra at gmail dot com
2020-10-12 8:23 ` marxin at gcc dot gnu.org
2020-10-12 9:28 ` aldyh at gcc dot gnu.org
2020-10-12 23:42 ` amodra at gmail dot com
2020-10-15 6:50 ` amodra at gmail dot com
2020-10-15 8:51 ` marxin at gcc dot gnu.org
2020-10-15 12:14 ` amodra at gmail dot com
2020-10-15 14:09 ` amacleod at redhat dot com
2020-10-16 12:17 ` rguenth at gcc dot gnu.org
2020-10-16 13:38 ` amacleod at redhat dot com
2020-10-16 13:48 ` rguenth at gcc dot gnu.org
2020-10-16 13:55 ` amacleod at redhat dot com
2020-10-16 13:58 ` rguenther at suse dot de
2020-10-16 14:17 ` amacleod at redhat dot com
2020-10-16 15:02 ` rguenther at suse dot de
2020-10-16 15:46 ` amacleod at redhat dot com
2020-10-16 16:55 ` rguenther at suse dot de
2020-10-16 17:00 ` amacleod at redhat dot com
2020-10-19 6:08 ` rguenth at gcc dot gnu.org
2020-10-19 13:29 ` bergner at gcc dot gnu.org
2020-10-19 18:45 ` bergner at gcc dot gnu.org
2020-10-19 19:47 ` amacleod at redhat dot com
2020-10-19 20:50 ` bergner at gcc dot gnu.org
2020-10-19 21:21 ` bergner at gcc dot gnu.org
2020-10-19 22:40 ` bergner at gcc dot gnu.org
2020-10-19 23:11 ` cvs-commit at gcc dot gnu.org
2020-10-19 23:28 ` amacleod at redhat dot com
2020-10-20 6:23 ` rguenth at gcc dot gnu.org
2020-10-20 14:16 ` bergner at gcc dot gnu.org
2020-10-20 14:41 ` rguenther at suse dot de
2020-10-20 16:03 ` bergner at gcc dot gnu.org
2020-10-20 20:27 ` segher at gcc dot gnu.org
2020-10-21 19:30 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-21 19:34 ` bergner at gcc dot gnu.org
2020-11-07 22:32 ` cvs-commit at gcc dot gnu.org
2020-11-07 22:36 ` bergner 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-97360-4-Cp9VM8diT7@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).