Calculation error.

[Ryster]

Hello.
I have such a problem. Well, the output of code running on 32-bit is different from that of code running on 64-bit. At the same time, it calculates incorrectly in the 64-bit version, and correctly in the 32-bit version. Is there any advice for this, or does it have to be.
Regards - Ryster

[bplus]

Hello.
I have such a problem. Well, the output of code running on 32-bit is different from that of code running on 64-bit. At the same time, it calculates incorrectly in the 64-bit version, and correctly in the 32-bit version. Is there any advice for this, or does it have to be.
Regards - Ryster

Say what the problem is, maybe it's been reported and there is a fix, maybe it needs to be fixed, maybe it's unfixable in near future.

So my advice is to please provide more details.

[SpriggsySpriggs]

Please paste the code you are using so we can help debug

[Ryster]

Perhaps this problem has already been raised. As I wrote. With the same input data, the result is different. Except that the 32-bit version counts correctly. I suspect a different rounding procedure inside the 64 bit compiler.

[SpriggsySpriggs]

We can't help you if you don't give us more info.

[SMcNeill]

My guess is it’s the difference in the floating point math used. 

Look at the code here, and see if it “corrects” the issue for you: https://qb64.freeforums.net/thread/134/change-floating-point-precision

[Ryster]

Thanks to SMcNeill, it is just like you wrote.
Regards - Ryster

[SMcNeill]

It’s the difference in 80-bit FPU math processing (32-bit machines) vs 64-bit SSE math processing (64-bit machines).  The code I provided should allow you to set what you need to get the results you’re looking for. 

[Ryster]

In my free time I will test and inform.

Regards - Ryster

[Pete]

Another stunning endorsement for string math!

Yep, it's going to be what Steve said. When we get to 128 bit encryption, it will probably be this problem all over again. That's why I like string math, with the exception it's bit of work to program.

Similar to this topic, I wonder what Ed's app he posted would do under this 32-bit 64-bit floating point difference?

Pete

[Ryster]

Double precision successfully solved the problem. The calculation is now valid on the 64-bit version. This error appeared sporadically, therefore it was difficult to notice it. It only occurred with certain numerical values. For example, the calculations for 1990 are correct and 2021 are incorrect. Thanks for your willingness to help.
Regards - Ryster