I don't have an M1 myself, but according to the data from the thread on
the lazarus mail list, there is a bug in the 3.3.1 asm generator for M1
var pn8: pint8; // pointer signed byte
In the below expression ...(not pn8^)...
"pn8^" is loaded to w0 and sign extended. From this point onwards
ope
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...
https://gitlab.com/freepas
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 maill
On Tue, Dec 28, 2021 at 9:41 AM Marc Weustink via fpc-devel
wrote:
>
> To be continued...
Wow..
Hats off to you.
--
Bart
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Hi all,
It took a bit longer than expected, but I'm happy to inform you that the
Lazarus services are back online.
For those interested in why it took longer, I'll explain at the end of
the message.
Marc
On 24-12-2021 08:30, Marc Weustink wrote:
Hi,
On Monday 27 December 9.00 CET (8.00 GMT
