On Monday, 19 June 2023 at 09:54:32 UTC, Iain Buclaw wrote:
On Sunday, 18 June 2023 at 02:55:32 UTC, Cecil Ward wrote:
On Friday, 16 June 2023 at 13:12:06 UTC, Iain Buclaw wrote:
Redundant jump? Yes, arguably. Leads to wrong runtime?
Doesn't look that way.
Completely agree with Iain, it’s n
On Sunday, 18 June 2023 at 02:55:32 UTC, Cecil Ward wrote:
On Friday, 16 June 2023 at 13:12:06 UTC, Iain Buclaw wrote:
Redundant jump? Yes, arguably. Leads to wrong runtime? Doesn't
look that way.
Completely agree with Iain, it’s not incorrect code, I wasn’t
intending to suggest that. I’d j
On Friday, 16 June 2023 at 13:12:06 UTC, Iain Buclaw wrote:
On Wednesday, 14 June 2023 at 12:35:43 UTC, Cecil Ward wrote:
I have just noticed a bug in the latest release of GDC that
targets x86-64. For example GDC 12.3 and above versions too,
running on X86-64, targeting self. This was built wi
On Wednesday, 14 June 2023 at 12:35:43 UTC, Cecil Ward wrote:
I have just noticed a bug in the latest release of GDC that
targets x86-64. For example GDC 12.3 and above versions too,
running on X86-64, targeting self. This was built with:
-O3 -frelease -march=alderlake
What leads you to bel
I have just noticed a bug in the latest release of GDC that
targets x86-64. For example GDC 12.3 and above versions too,
running on X86-64, targeting self. This was built with:
-O3 -frelease -march=alderlake
Generated code is:
je L1
jbe L1
…
…
L1: ret
The probably reason for
