However FPC implementation makes inconsistent the values returned from
OpenBit with those obtained reading Size.
Do I miss some point?
I can imagine bits being allocated in words to avoid endianess problems. So
it could be a deliberate deviation for portabilities sake.
Marco van de Voort ha scritto:
However FPC implementation makes inconsistent the values returned from
OpenBit with those obtained reading Size.
Do I miss some point?
I can imagine bits being allocated in words to avoid endianess problems. So
it could be a deliberate deviation for
On Fri, 25 Jan 2008, Giuliano Colla wrote:
Marco van de Voort ha scritto:
However FPC implementation makes inconsistent the values returned from
OpenBit with those obtained reading Size.
Do I miss some point?
I can imagine bits being allocated in words to avoid endianess
Michael Van Canneyt ha scritto:
Please submit a patch to me. I'll review and apply it.
O.K. Provided I succeed ;-) , I'll do it.
Giuliano
--
Giuliano Colla
Whenever people agree with me, I always feel I must be wrong (O. Wilde)
___
fpc-devel
Hi Folks,
I have a 32 bit system running openSUSE 10.3 with FPC 2.2.0 installed on
it. On the other system the 64 bit variants installed of the OS and the
compiler. I have a code that compiles and runs fine in the 32 bit
environment. The same code compiles on 64-bit but it hits a division by
On 25 Jan 2008, at 16:30, Miklos Cserzo wrote:
I guess the real problem is well before the critical line but I have
no idea where could it be and how to find it. Now I wonder, if the
same code supposed to compile and run in the same manner on 32 and
64 bit architecture? Is this sort of
