On Fri, Jul 27, 2018 at 10:07:20AM -0500, Kelvin Nilsen wrote: > On 7/26/18 9:54 AM, Segher Boessenkool wrote: > > On Thu, Jul 26, 2018 at 08:40:01AM -0500, Kelvin Nilsen wrote: > >> To improve internal consistency and to improve consistency with published > >> ABI documents, this patch replaces the __uint128_t type with __uint128 and > >> replaces __int128_t with __int128. > > > >> Is this ok for trunk? > > > > Looks good, thanks! Most (all?) of these functions are not documented > > in the ABI, but this is a step forward anyway. Okay for trunk. > > > > What do things like error messages involving these functions look like? > > What types do those say? > > Thanks for review and approval. To respond to your question about error > messages: > > > > microdoc3.c:22:3: error: invalid parameter combination for AltiVec > > intrinsic ‘__builtin_vec_vaddcuq’ > > u1 = vec_vaddcuq (d2, d3); > > ^~
Ah, so no type at all. Well that's good :-) Thanks, Segher
