From: aldyh <aldyh@redhat.com>
To: "carlo.bonzini@libero.it" <carlo.bonzini@libero.it>
Cc: bonzini <bonzini@gnu.org>, rth <rth@redhat.com>, gcc@gcc.gnu.org
Subject: Re: altivec still broken?!
Date: Thu, 29 Apr 2004 16:39:00 -0000 [thread overview]
Message-ID: <20040429142639.GE14457@redhat.com> (raw)
In-Reply-To: <HWXRPR$155B48652FCC799C9F3CD6AD93475DFB@libero.it>
On Thu, Apr 29, 2004 at 04:17:51PM +0200, carlo.bonzini@libero.it wrote:
(copying list)
> > Are you changing the behavior of opaque types?
>
> No, except with respect to __builtin_types_compatible_p, which does not happen
> anyway because AltiVec does not use them.
Let me see if I get this right...
You are changing the behavior of opaque types with respect to
__builtin_types_compatible_p? If so, we don't really care about a
change in this functionality because SPE uses opaque types but does
NOT use __builtin_types_compatible_p. So, nothing changes.
OTOH, if you change the behavior of opaque types wrt
__builtin_types_compatible_p, this doesn't affect AltiVec either
because AltiVec uses __builtin_types_compatible_p but does NOT use
opaque types.
Agreed?
If so, why the change at all. What code would it affect?
Aldy
next parent reply other threads:[~2004-04-29 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HWXRPR$155B48652FCC799C9F3CD6AD93475DFB@libero.it>
2004-04-29 16:39 ` aldyh [this message]
2004-04-30 15:32 ` Paolo Bonzini
2004-04-30 15:47 ` Paolo Bonzini
2004-04-27 0:56 Aldy Hernandez
2004-04-27 11:07 ` Paolo Bonzini
2004-04-27 11:55 ` Paolo Bonzini
2004-04-27 22:15 ` Aldy Hernandez
2004-04-29 20:10 ` Paolo Bonzini
2004-04-29 21:21 ` Ziemowit Laski
2004-04-30 10:56 ` Paolo Bonzini
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=20040429142639.GE14457@redhat.com \
--to=aldyh@redhat.com \
--cc=bonzini@gnu.org \
--cc=carlo.bonzini@libero.it \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).