Messages in this thread | ![/](/images/icornerl.gif) | | From | "H. Peter Anvin" <> | Subject | Re: [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial) | Date | 6 Nov 2003 15:40:48 -0800 |
| |
Followup to: <20031106143110.6231ecde.davem@redhat.com> By author: "David S. Miller" <davem@redhat.com> In newsgroup: linux.dev.kernel > > On 6 Nov 2003 12:40:55 -0800 > "H. Peter Anvin" <hpa@zytor.com> wrote: > > > Note that "long long" (the underlying type) is valid > > standards-compliant C99. gcc can handle it when in C89 mode if > > defined as __extension__ long long IIRC. > > That's correct and I've suggested this. > > But keep in mind that people with non-GCC compilers will then > start complaining. >
So...
#ifdef __GNUC__ # define __gcc_extension __extension__ #else # define __gcc_extension #endif
typedef __gcc_extension signed long long s32; typedef __gcc_extension unsigned long long u32;
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! If you send me mail in HTML format I will assume it's spam. "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |