Why MaxDouble does not equal to MaxDouble?

[Thaddy]

Not, yet, but it should not be difficult to find.

[bytebites]

Is there a bingo program too?

[tetrastes]

From https://learn.microsoft.com/en-us/cpp/build/ieee-floating-point-representation?view=msvc-170:

The IEEE standard also specifies half-precision (2-byte) and quadruple-precision (16-byte) formats, and a double-extended-precision (10-byte) format, which some C and C++ compilers implement as the long double data type. In the MSVC compiler, the long double data type is treated as a distinct type, but the storage type maps to double. There is, however, intrinsic and assembly language support for computations using the other formats, including the double-extended-precision format, where supported by hardware.

So Windows x86_64 ABI does not deprecate the x87 CPU, it, say that, doesn't bother much about that.

[Thaddy]

Is there a bingo program too?

Well at least the algorithm demo was already published and and that did everybody else wrong. It will come.

[Zoran]

If you can not find it on the forum, it is probably on the mailing list.
I could not find it quickly  myself too, but I know it is there.

Much Talk. No show. ;-)

Now this is really rude.

Thaddy told you he remembers there were some instructions that might interest you.
Although he could not find it, the fact that he had seen it once might be helpful to you, so you can try to search, if you are interested.
He might help more and try to find it, but he certainly does not owe that to you.

[TRon]

I was able to find this though expressed by PascalDragon.

Took about 15 second to find with ddg 

[BrunoK]

Now this is really rude.

Thaddy told you he remembers there were some instructions that might interest you.

Thaddy bla bla remembers bla bla has written knows all was chief bla bla others are idiots blabla ready to run bla bla. Thaddy knows all.

What Thaddy puts here is usually buggy and very very occasionally ok.

[BrunoK]

I was able to find this though expressed by PascalDragon.

Took about 15 second to find with ddg 

Thank you, noted and investigating based on your reply and asssociated link.

B.

[BrunoK]

I was able to find this though expressed by PascalDragon.

Took about 15 second to find with ddg 

That is the decisive link.

-dFPC_SUPPORT_X87_TYPES_ON_WIN64 when rebuilding FPC (3.2.2 on win64) solves also the Currency * Currency ending in wrong values for large numbers.

Best of all worlds, uses 64bit double for Double calculations, and Extended for Extended data types. I didn't dig for other 87FPU functions.

Doesn't look to be penalizing in terms of speed.

Thanks.

[PascalDragon]

3. One reason for sticking with 32-bit apps is that the Extended type and FPU are supported.

Then you also shouldn't use non-x86 processors, because the x86 family is the only one that supports 80-bit floating point (well, m68k supports it as well, but it has a slightly different format).

[BrunoK]

3. One reason for sticking with 32-bit apps is that the Extended type and FPU are supported.

Then you also shouldn't use non-x86 processors, because the x86 family is the only one that supports 80-bit floating point (well, m68k supports it as well, but it has a slightly different format).

So you also should throw 80 bit float out or Linux x86_64 FPC.
Why dont you do it ?

[PascalDragon]

Why dont you do it ?

Simple: Backwards compatibility.

[BrunoK]

Why dont you do it ?

Simple: Backwards compatibility.

Nice Joke.

[MarkMLl]

Now this is really rude.

Thaddy told you he remembers there were some instructions that might interest you.

I suggest that "Go Forth and multiply", implying postfix notation, is not entirely in the spirit of a forum devoted to Pascal >:-)

MarkMLl