This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: altivec still broken?!
- From: aldyh <aldyh at redhat dot com>
- To: "carlo dot bonzini at libero dot it" <carlo dot bonzini at libero dot it>
- Cc: bonzini <bonzini at gnu dot org>, rth <rth at redhat dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 29 Apr 2004 10:26:39 -0400
- Subject: Re: altivec still broken?!
- References: <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