This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Hi Kumar,
> > Nick also has a patch (that I'm not too fond off, but I *could*
> > consider if there's no other way), that looks at the typedef name
> > ("__ev64_u64__" in this case) to determine where arguments should go.
> I did NOT think that Nick's patch looked at the typedef name, but
> introduced a V1DImode, and used that to handle these cases, but I
> could have missed something in it.
Just to clear up this point. I created *two* patches. The first one
is the one Aldy is referring two, and it was indeed a terrible hack
that performed a strncmp() on the type name.
The second patch replaced the first patch and created a new vector
type: V1D1 which then behaved as Motorola wanted. This second
patch is much cleaner, and might even be suitable for submission to
the FSF if the idea of single element vectors is accepted.
Cheers
Nick
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |