On Sat, Jan 1, 2022 at 1:21 PM Jonas Maebe via fpc-devel
wrote:
> > And the consequence is that even if we eventually have native 128-bit
> > integer support, the problem will persist but now for Int128?
>
> Yes, unless we would only support/use it for intermediate results.
Thanks for
On 01/01/2022 13:01, Bart via fpc-devel wrote:
OK, let me see if I understand it correctly now:
1. (Signed) Int64 := unsigned(32-16-8bit) + unsigned(32-16-8-bit) +
signed(32-16-8-bit)
gets evaluated with unsigned 64-bit arithmetic and then the test for
Correct.
How to workaround (1) then,
On Thu, Dec 30, 2021 at 1:05 PM Jonas Maebe via fpc-devel
wrote:
> > Nor why it only triggers with Byte + Byte + Unsigned, and not with
>
> In you original mail, you said it triggered for Byte + Byte + Signed.
Yes, of course, the original mail is correct.
> It doesn't trigger for Byte +
On 28/12/2021 22:51, Bart via fpc-devel wrote:
On Tue, Dec 28, 2021 at 9:38 PM Jonas Maebe via fpc-devel
wrote:
https://gitlab.com/freepascal.org/fpc/source/-/issues/37875
OK, but from reading that it is still unclear to me wether this is a bug or not.
It's something that is annoying, but
On Tue, Dec 28, 2021 at 9:38 PM Jonas Maebe via fpc-devel
wrote:
>
> https://gitlab.com/freepascal.org/fpc/source/-/issues/37875
OK, but from reading that it is still unclear to me wether this is a bug or not.
Nor why it only triggers with Byte + Byte + Unsigned, and not with
Byte + Unsigned.
On 2021-12-28 14:47, Bart via fpc-devel wrote:
On Mon, Jun 28, 2021 at 8:33 PM Bart wrote:
Int64 := Byte + Byte + (Signed integer type (8,16 or 32 bit) with
value < 0) will always give a range check error on X86_64 platform (if
range checking is enabled).
Bump...
On Mon, Jun 28, 2021 at 8:33 PM Bart wrote:
> Int64 := Byte + Byte + (Signed integer type (8,16 or 32 bit) with
> value < 0) will always give a range check error on X86_64 platform (if
> range checking is enabled).
Bump...
--
Bart
___
fpc-devel
