Re: quad_t and portability

1999-08-09 Thread Brian F. Feldman
On Mon, 9 Aug 1999, Tony Finch wrote: > "Brian F. Feldman" wrote: > > > >Is there anyone who is specifically checking for long long > >C9X-compliancy in the source tree (mainly libc)? > > I started reviewing libc for C9X features in general -- a fair amount > of work is required to update macros

Re: quad_t and portability

1999-08-09 Thread Brian F. Feldman
On Mon, 9 Aug 1999, Tony Finch wrote: > "Brian F. Feldman" <[EMAIL PROTECTED]> wrote: > > > >Is there anyone who is specifically checking for long long > >C9X-compliancy in the source tree (mainly libc)? > > I started reviewing libc for C9X features in general -- a fair amount > of work is requi

Re: quad_t and portability

1999-08-09 Thread Tony Finch
"Brian F. Feldman" wrote: > >Is there anyone who is specifically checking for long long >C9X-compliancy in the source tree (mainly libc)? I started reviewing libc for C9X features in general -- a fair amount of work is required to update macros and typedefs in (plus the new ). Doing a thorough

Re: quad_t and portability

1999-08-09 Thread Tony Finch
"Brian F. Feldman" <[EMAIL PROTECTED]> wrote: > >Is there anyone who is specifically checking for long long >C9X-compliancy in the source tree (mainly libc)? I started reviewing libc for C9X features in general -- a fair amount of work is required to update macros and typedefs in (plus the new )

Re: quad_t and portability

1999-08-07 Thread Brian F. Feldman
On Sat, 7 Aug 1999, John Polstra wrote: > In article <19990807165202.a37...@cicely8.cicely.de>, > Bernd Walter wrote: > > On Sat, Aug 07, 1999 at 05:38:48PM +0800, Peter Wemm wrote: > > > > > > But not on the Alpha... int64_t is a long there, and gcc complains unless > > > you use %ld. > > Mmm

Re: quad_t and portability

1999-08-07 Thread Brian F. Feldman
On Sat, 7 Aug 1999, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Bernd Walter <[EMAIL PROTECTED]> wrote: > > On Sat, Aug 07, 1999 at 05:38:48PM +0800, Peter Wemm wrote: > > > > > > But not on the Alpha... int64_t is a long there, and gcc complains unless > > > you use %ld. > > Mmm a

Re: quad_t and portability

1999-08-07 Thread John Polstra
In article <19990807165202.a37...@cicely8.cicely.de>, Bernd Walter wrote: > On Sat, Aug 07, 1999 at 05:38:48PM +0800, Peter Wemm wrote: > > > > 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. No, longs are 64 bits on

Re: quad_t and portability

1999-08-07 Thread John Polstra
In article <[EMAIL PROTECTED]>, Bernd Walter <[EMAIL PROTECTED]> wrote: > On Sat, Aug 07, 1999 at 05:38:48PM +0800, Peter Wemm wrote: > > > > 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. No, longs are 64 bits on th

Re: quad_t and portability

1999-08-07 Thread Brian F. Feldman
On Sat, 7 Aug 1999, Warner Losh wrote: > In message > "Brian F. Feldman" writes: > : Sorry, kinda used to quad rather than long long. I'm pretty sure ll > : isn't yet supported by the kernel printf functions... > > You may be right about that. The simple solution to this, which I'd like to see

Re: quad_t and portability

1999-08-07 Thread Doug Rabson
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 fo

Re: quad_t and portability

1999-08-07 Thread Brian F. Feldman
On Sat, 7 Aug 1999, 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

Re: quad_t and portability

1999-08-07 Thread Brian F. Feldman
On Sat, 7 Aug 1999, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Brian F. >Feldman" writes: > : Sorry, kinda used to quad rather than long long. I'm pretty sure ll > : isn't yet supported by the kernel printf functions... > > You may be right about that. The simple solution to this, wh

Re: quad_t and portability

1999-08-07 Thread Doug Rabson
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 f

Re: quad_t and portability

1999-08-07 Thread Brian F. Feldman
On Sat, 7 Aug 1999, 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

Re: quad_t and portability

1999-08-07 Thread Jonathan Lemon
In article you write: >In message "Brian >F. Feldman" writes: >: You can always use off_t with "%qd", (int64_t)foo. > >But that isn't portbale. %qd is a bsdism. %lld and %llu are the >latest C standards way to say that. Still isn't portable. DEC Alphas use "%ld", and don't know about "%lld

Re: quad_t and portability

1999-08-07 Thread Jonathan Lemon
In article [EMAIL PROTECTED]> you write: >In message <[EMAIL PROTECTED]> "Brian F. >Feldman" writes: >: You can always use off_t with "%qd", (int64_t)foo. > >But that isn't portbale. %qd is a bsdism. %lld and %llu are the >latest C standards way to say that. Still isn't portable. DEC Alphas

Re: quad_t and portability

1999-08-07 Thread Bernd Walter
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 us

Re: quad_t and portability

1999-08-07 Thread Bernd Walter
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 u

Re: quad_t and portability

1999-08-07 Thread Peter Wemm
"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 se

Re: quad_t and portability

1999-08-07 Thread Peter Wemm
"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 s

Re: quad_t and portability

1999-08-06 Thread Patryk Zadarnowski
> In message > "Brian F. Feldman" writes: > : You can always use off_t with "%qd", (int64_t)foo. > > But that isn't portbale. %qd is a bsdism. %lld and %llu are the > latest C standards way to say that. If you're that fixed on portability, "%lux%08ulx", (long)foo>>32, (long)foo is alwa

Re: quad_t and portability

1999-08-06 Thread Warner Losh
In message "Brian F. Feldman" writes: : Sorry, kinda used to quad rather than long long. I'm pretty sure ll : isn't yet supported by the kernel printf functions... You may be right about that. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the

Re: quad_t and portability

1999-08-06 Thread Brian F. Feldman
On Sat, 7 Aug 1999, Warner Losh wrote: > In message > "Brian F. Feldman" writes: > : You can always use off_t with "%qd", (int64_t)foo. > > But that isn't portbale. %qd is a bsdism. %lld and %llu are the > latest C standards way to say that. Sorry, kinda used to quad rather than long long. I

Re: quad_t and portability

1999-08-06 Thread Warner Losh
In message "Brian F. Feldman" writes: : You can always use off_t with "%qd", (int64_t)foo. But that isn't portbale. %qd is a bsdism. %lld and %llu are the latest C standards way to say that. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the

Re: quad_t and portability

1999-08-06 Thread Alex Zepeda
On Fri, 6 Aug 1999, Don Lewis wrote: > 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 ... sizeof() perhaps? - alex To Unsubscribe: send mail to majord...@freebsd.org w

Re: quad_t and portability

1999-08-06 Thread Patryk Zadarnowski
> In message <[EMAIL PROTECTED]> "Brian F. >Feldman" writes: > : You can always use off_t with "%qd", (int64_t)foo. > > But that isn't portbale. %qd is a bsdism. %lld and %llu are the > latest C standards way to say that. If you're that fixed on portability, "%lux%08ulx", (long)foo>>32,

Re: quad_t and portability

1999-08-06 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Brian F. Feldman" writes: : Sorry, kinda used to quad rather than long long. I'm pretty sure ll : isn't yet supported by the kernel printf functions... You may be right about that. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-

Re: quad_t and portability

1999-08-06 Thread Brian F. Feldman
On Sat, 7 Aug 1999, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Brian F. >Feldman" writes: > : You can always use off_t with "%qd", (int64_t)foo. > > But that isn't portbale. %qd is a bsdism. %lld and %llu are the > latest C standards way to say that. Sorry, kinda used to quad rathe

Re: quad_t and portability

1999-08-06 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Brian F. Feldman" writes: : You can always use off_t with "%qd", (int64_t)foo. But that isn't portbale. %qd is a bsdism. %lld and %llu are the latest C standards way to say that. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-

Re: quad_t and portability

1999-08-06 Thread Brian F. Feldman
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

Re: quad_t and portability

1999-08-06 Thread Alex Zepeda
On Fri, 6 Aug 1999, Don Lewis wrote: > 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 ... sizeof() perhaps? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: quad_t and portability

1999-08-06 Thread Brian F. Feldman
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 > } mor

Re: quad_t and portability

1999-08-06 Thread Don Lewis
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 por

Re: quad_t and portability

1999-08-06 Thread Don Lewis
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 po

RE: quad_t and portability

1999-08-06 Thread Alton, Matthew
> -Original Message- > From: Sheldon Hearn [SMTP:sheld...@uunet.co.za] > Sent: Friday, August 06, 1999 8:34 AM > To: freebsd-hackers@freebsd.org > Subject: Re: quad_t and portability > > > > On Fri, 06 Aug 1999 15:29:25 +0200, Sheldon Hearn wrote: &g

RE: quad_t and portability

1999-08-06 Thread Alton, Matthew
> -Original Message- > From: Sheldon Hearn [SMTP:[EMAIL PROTECTED]] > Sent: Friday, August 06, 1999 8:34 AM > To: [EMAIL PROTECTED] > Subject: Re: quad_t and portability > > > > On Fri, 06 Aug 1999 15:29:25 +0200, Sheldon Hearn wrote: > > > I

Re: quad_t and portability

1999-08-06 Thread Sheldon Hearn
On Fri, 06 Aug 1999 15:29:25 +0200, Sheldon Hearn wrote: > 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. Yes yes, before you jump on my head, I meant u_quad_t. :-) Ciao,

Re: quad_t and portability

1999-08-06 Thread Sheldon Hearn
On Fri, 06 Aug 1999 15:29:25 +0200, Sheldon Hearn wrote: > 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. Yes yes, before you jump on my head, I meant u_quad_t. :-) Ciao,