Date: Sat, 7 Aug 1999 20:03:15 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Bernd Walter <ticso@cicely.de> Cc: Peter Wemm <peter@netplex.com.au>, "Brian F. Feldman" <green@freebsd.org>, Don Lewis <Don.Lewis@tsc.tdk.com>, Sheldon Hearn <sheldonh@uunet.co.za>, freebsd-hackers@freebsd.org Subject: Re: quad_t and portability Message-ID: <Pine.BSF.4.10.9908072002390.50383-100000@salmon.nlsystems.com> In-Reply-To: <19990807165202.A37288@cicely8.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 7 Aug 1999, Bernd Walter wrote: > On Sat, Aug 07, 1999 at 05:38:48PM +0800, Peter Wemm wrote: > > "Brian F. Feldman" wrote: > > > On Fri, 6 Aug 1999, Don Lewis wrote: > > > > > > > On Aug 6, 3:29pm, Sheldon Hearn wrote: > > > > } Subject: quad_t and portability > > > > } > > > > } Hi folks, > > > > } > > > > } I want to patch wc(1) so that it uses quad_t instead of u_long. This is > > > > } necessary if wc(1) is to produce sensible results for files containing > > > > } more than 4GB of data. > > > > > > > > Why not off_t, which should be portable and scale properly with the > > > > maximum system file size. Then the only problem is figuring a portable > > > > means of printing the result ... > > > > > > > > > > You can always use off_t with "%qd", (int64_t)foo. > > > > But not on the Alpha... int64_t is a long there, and gcc complains unless > > you use %ld. > Mmm and long is 32Bit it seems. > At least that would explain some of the warnings I got when setting MAXDSIZ to > 128G on alpha. Long is 64bit, int is 32bit on the alpha. Use u_int64_t to specify the bitsize. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9908072002390.50383-100000>