I'm not certain if the size of data types such as ints and pointers
will expand to 64-bits in the compiler. I don't find that likely since
I'm pretty sure that pointers are 64 bit on most 64 bit architectures.
Likewise, long int. int is normally still 32 bit.
Code that assumes anything
Jonathan Polley wrote:
Now that 64-bit processors are becoming more
available, does anyone
know
of any problems that FlightGear may have running on
a 64-bit
processor
(Opteron or PowerPC 970)? I am assuming that those
areas that would
be
sensitive to data sizes (i.e., file formats) are
safe?
Gopal Mor wrote:
Solution : Use pragma pack(n)
That won't work on all compilers.
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Jonathan Polley wrote:
Now that 64-bit processors are becoming more available, does anyone know
of any problems that FlightGear may have running on a 64-bit processor
(Opteron or PowerPC 970)? I am assuming that those areas that would be
sensitive to data sizes (i.e., file formats) are safe?
On Friday, June 13, 2003, at 02:49 AM,
[EMAIL PROTECTED] wrote:
Message: 9
Date: Thu, 12 Jun 2003 22:21:46 -0500
From: Jonathan Polley [EMAIL PROTECTED]
Subject: [Flightgear-devel] 64-Bit Question
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII
On Thu, Jun 12, 2003 at 10:21:46PM -0500, Jonathan Polley wrote:
Now that 64-bit processors are becoming more available, does anyone
know of any problems that FlightGear may have running on a 64-bit
processor (Opteron or PowerPC 970)? I am assuming that those areas
that would be sensitive
Now that 64-bit processors are becoming more available, does anyone
know of any problems that FlightGear may have running on a 64-bit
processor (Opteron or PowerPC 970)? I am assuming that those areas
that would be sensitive to data sizes (i.e., file formats) are safe?
Jonathan Polley
