On 07/01/11 21:49, Joseph S. Myers wrote: > On Fri, 1 Jul 2011, Bernd Schmidt wrote: > >> * Should we add an __int40_t keyword, or just do a pushdecl for it? >> The patch currently does the latter to match __int128_t, but >> decimal float and fixed-point support uses keywords. This may make >> a difference for (existing) code using "unsigned __int40_t". > > My advice is neither, initially; leave it to the user to define typedefs > using the mode (possibly providing a header that the user can include with > -include). __int128_t is legacy and undocumented, with the __int128 > keyword (from the x86_64 ABI) being preferred. I also don't recommend > adding any types to stdint.h (so eliminating a lot more of the > complexity); there is no requirement to have those types there,
Well, this was done for compatibility with an existing toolchain (which unfortunately also allows "unsigned __int40_t"). I guess I could be persuaded that we don't care enough and people must include "c6x_intrinsics.h" when using gcc. > and in any case libc's stdint.h is used in most cases instead of GCC's That just means we'd have to modify newlib and uClibc as well if we wanted to support this. > Don't try to understand anything about stdint.h with reference to C99 > versions before TC3; there were several defects fixed in the TCs. Is this available anywhere (even if only inside CS?) Bernd
