From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nathan Sidwell <nathan@acm.org>
Cc: Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
Richard Biener <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PR 79905] ICE with vector_type
Date: Thu, 06 Apr 2017 20:18:00 -0000 [thread overview]
Message-ID: <20170406201743.GR4402@gate.crashing.org> (raw)
In-Reply-To: <f334e863-5702-f13d-5a04-90cd88459b21@acm.org>
Hi!
On Thu, Apr 06, 2017 at 02:34:03PM -0400, Nathan Sidwell wrote:
> Segher, this fixes a C++ ICE where TYPE_CANONICALs didn't match, but the
> types were the same (and non-structural comparison). The underlying
> cause is that types with different TYPE_NAME are considered different
> canonical types. add_builtin_type smacked TYPE_NAME of the canonical
> type, therefore guaranteeing that any subsequent vector types would be
> thought of as different.
> Index: config/rs6000/rs6000.c
> ===================================================================
> --- config/rs6000/rs6000.c (revision 246647)
> +++ config/rs6000/rs6000.c (working copy)
> @@ -17257,6 +17257,22 @@ rs6000_expand_builtin (tree exp, rtx tar
> gcc_unreachable ();
> }
>
> +/* Create a builtin vector type with a name. Taking care not to give
> + the canonical type a name. */
> +
> +static tree
> +rs6000_vt (const char *name, tree elt_type, unsigned num_elts)
I don't like this cryptic name very much. Maybe you could just use a
longer name and indent differently (break at the "=" for example), or
do a macro around where it is used a lot?
But, okay for trunk whatever you decide on this. Thanks!
Segher
next prev parent reply other threads:[~2017-04-06 20:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 19:03 Nathan Sidwell
2017-04-04 8:28 ` Richard Biener
2017-04-04 11:31 ` Nathan Sidwell
2017-04-04 13:00 ` Richard Biener
2017-04-04 13:49 ` Nathan Sidwell
2017-04-04 13:57 ` Bill Schmidt
2017-04-04 14:02 ` Nathan Sidwell
2017-04-04 17:40 ` Bill Schmidt
2017-04-04 18:02 ` Nathan Sidwell
2017-04-04 20:46 ` Bill Schmidt
2017-04-05 13:18 ` Nathan Sidwell
2017-04-05 13:35 ` Bill Schmidt
2017-04-05 14:14 ` Nathan Sidwell
2017-04-05 20:33 ` Bill Schmidt
2017-04-06 10:29 ` Richard Biener
2017-04-06 11:28 ` Nathan Sidwell
2017-04-06 14:04 ` Richard Biener
2017-04-06 14:20 ` Bill Schmidt
2017-04-06 14:26 ` Bill Schmidt
2017-04-06 15:13 ` Bill Schmidt
2017-04-06 18:34 ` Nathan Sidwell
2017-04-06 20:18 ` Segher Boessenkool [this message]
2017-04-10 11:24 ` Nathan Sidwell
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=20170406201743.GR4402@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
--cc=richard.guenther@gmail.com \
--cc=wschmidt@linux.vnet.ibm.com \
/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).