I can also confirm that the original test case posted works correctly when moving the file from Linux to Sparc (Solaris) and PA-RISC (HP-UX).
-Tom > -----Original Message----- > From: D. Richard Hipp [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 18, 2005 2:21 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Possible bug regarding endiannes and > realstorageclass (sqlite3) > > On Thu, 2005-08-18 at 14:10 -0400, D. Richard Hipp wrote: > > On Thu, 2005-08-18 at 09:40 -0700, Robert Simpson wrote: > > > http://www.psc.edu/general/software/packages/ieee/ieee.html > > > > > > The way I interpreted this site, is that the IEEE > standard for floating > > > point numbers was processor agnostic and the storage of > the bits went from > > > left to right. > > > > > > > I wrote a test program to print out the byte values for 1.0 and 1 > > on both ix86 (Intel, Linux) and powerpc (G5, OS-X). The results: > > > > ix86: 000000000000f03f 0100000000000000 > > powerpc: 3ff0000000000000 0000000000000001 > > > > This seems to validate the approach taken by SQLite, which is to > > byteswap floating point values on ix86 machines. > > > > As a double-check, I have confirmed that floating-point values > written into an SQLite3 database file written on intel/linux > are readable on max/os-x and vice versa. > -- > D. Richard Hipp <[EMAIL PROTECTED]> > >
