public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Nathan Sidwell <nathan@acm.org>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PR 79905] ICE with vector_type
Date: Thu, 06 Apr 2017 15:13:00 -0000	[thread overview]
Message-ID: <CCA27AA9-1360-44BC-B33B-94DE025B2037@linux.vnet.ibm.com> (raw)
In-Reply-To: <174640D1-4C16-41F2-BBB2-70DD72B2941C@linux.vnet.ibm.com>


> On Apr 6, 2017, at 9:26 AM, Bill Schmidt <wschmidt@linux.vnet.ibm.com> wrote:
> 
> 
>> On Apr 6, 2017, at 9:19 AM, Bill Schmidt <wschmidt@linux.vnet.ibm.com> wrote:
>> 
>> 
>>> On Apr 6, 2017, at 9:04 AM, Richard Biener <richard.guenther@gmail.com> wrote:
>>> 
>>> On Thu, Apr 6, 2017 at 1:28 PM, Nathan Sidwell <nathan@acm.org> wrote:
>>>> Let's try this one then.
>> 
>> Nathan's patch regstraps cleanly.  I'll try Richard's variant (dropping the if test below) now.

As expected, this version passes regstrap as well.

Bill
> 
> FYI, the test case should also include:
> 
> // { dg-require-effective-target powerpc_altivec_ok } 
> 
> to avoid problems on targets without AltiVec support.
> 
> Bill
>> 
>> Bill
>>> 
>>> I'd call this
>>> 
>>> +  if (result == TYPE_CANONICAL (result))
>>> +    /* Copy so we don't give the canonical type a name.  */
>>> +    result = build_variant_type_copy (result);
>>> 
>>> premature optimization -- I wonder if anything breaks if you always copy?
>>> (that is, I expect result is always the canonical type here?)
>>> 
>>> Richard.
>>> 
>>>> nathan
>>>> 
>>>> --
>>>> Nathan Sidwell
>>> 
>> 
> 

  reply	other threads:[~2017-04-06 15:13 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 [this message]
2017-04-06 18:34                                       ` Nathan Sidwell
2017-04-06 20:18                                         ` Segher Boessenkool
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=CCA27AA9-1360-44BC-B33B-94DE025B2037@linux.vnet.ibm.com \
    --to=wschmidt@linux.vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nathan@acm.org \
    --cc=richard.guenther@gmail.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).