Ethereal-dev: Re: [Ethereal-dev] Diameter Finally up to -07

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Harris <gharris@xxxxxxxxx>
Date: Mon, 30 Jul 2001 22:49:43 -0700
On Tue, Jul 31, 2001 at 07:46:05AM +0200, Dr. Uwe Girlich wrote:
> SINIX-M (32 bit, runs on i386) wont ever support 64 bit data types.

Does GCC 2.x run on, and generate code for, SINIX-M machines?  If so,
with GCC you can get support for 64-bit integral data types (that's the
only 64-bit data type support that matters here), although you'd need
the GCC run-time library for those functions not done with inline code
(multiplies and divides, for example), and you won't get support in
"printf"/"sprintf". 

(Then again, even on platforms that *do* have 64-bit support, there's no
guaranteed way of printing them with "printf" - most support
"%ll[douxX]", but some use "%q[douXx]" instead.)

With the native compiler, you might not get 64-bit integral data type
support, however.

> > Is it no longer the case that there are platforms where you
> > don't have 64-bit integral data types with all the compilers people
> > would want to use, or should we try to come up with some way to support
> > them (e.g., displaying 64-bit quantities as raw strings of hex digits)?
> 
> The glib gives us G_HAVE_GINT64, so we could always check.

Yes, that's what I was thinking of using to check.

We'd also have to add our own configure-script check for the format to
use to print 64-bit integral data types (and perhaps handle the case of
"printf" not supporting it at all).