Date: Thu, 28 May 1998 10:43:49 +1000 From: Bruce Evans <bde@zeta.org.au> To: current@FreeBSD.ORG, eivind@yes.no Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Message-ID: <199805280043.KAA29573@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> > I think making it support e.g. 'long long' would need modifications of >> > the frontend. >> >> lcc, now at 4.0, still has the same problem I think. > >That's basically because "long long" is in total violation of the ISO >standard, IIRC. It will be standard in the next version of the standard :-(. >I've sent off a mail to the contact person for the TenDRA team; I'll >wait and see that they say about the feasibility of using TenDRA as an >OS compiler. I use __attribute__(()) to avoid warnings for `long long' so that LINT can be compiled by `gcc -ansi -pedantic' with no errors and only about 3000 lines of warnings. E.g., in <machine/types.h>. #ifdef __GNUC__ /* XXX <sys/cdefs.h> scope */ typedef int __attribute__((__mode__(__DI__))) int64_t; typedef unsigned int __attribute__((__mode__(__DI__))) u_int64_t; #else typedef long int64_t; /* XXX WRONG */ typedef unsigned long u_int64_t; /* XXX WRONG */ #endif Does TENDRA support __attribute__(())? I thought not :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805280043.KAA29573>