Re: GDC for ARM MacOS / OSX

On Thursday, 29 June 2023 at 09:18:19 UTC, Iain Buclaw wrote: On Thursday, 29 June 2023 at 05:27:57 UTC, Cecil Ward wrote: I tried getting GCC on my ARM M2 Mac using the homebrew package manager, which is how I got LDC. It gave me C++ and C and FORTRAN, but no sign of any GDC. How is GCC

GDC for ARM MacOS / OSX

I tried getting GCC on my ARM M2 Mac using the homebrew package manager, which is how I got LDC. It gave me C++ and C and FORTRAN, but no sign of any GDC.

Re: bug report x86-64 code: je / jbe

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

bug report x86-64 code: je / jbe

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

Regression - quality of generated x86-64 code between GDC v12.3 and v13.1

I wrote a very small procedure in D and the x86-64 asm code generated in GDC 12.3 was excellent whereas that from 13.1 was insanely bloated, totally different. Note: the badness is independent of the -On optimisation level (-O3 used initially.) Here’s the D code and following it, two asm code

Re: Hello world in AAarch64 Debian Buster

On Thursday, 8 August 2019 at 01:17:53 UTC, Cecil Ward wrote: On Wednesday, 7 August 2019 at 05:48:49 UTC, Iain Buclaw wrote: You could raise a Debian bug report, saying that aarch64 is in the libphobos supported list. Thanks Iain, I went through the prompts in the Debian bug report

Re: Hello world in AAarch64 Debian Buster

On Wednesday, 7 August 2019 at 05:48:49 UTC, Iain Buclaw wrote: You could raise a Debian bug report, saying that aarch64 is in the libphobos supported list. Thanks Iain, I went through the prompts in the Debian bug report program and I hope that that has emailed a report to them which

Re: Hello world in AAarch64 Debian Buster

On Tuesday, 6 August 2019 at 16:35:21 UTC, Johannes Pfau wrote: Am Tue, 06 Aug 2019 05:13:11 + schrieb Cecil Ward: I have a raspberry pi 3B+ running raspbian stretch 32-bit with a containerised guest o/s inside it using systemd-nspawn, the guest o/s being AAarch64 Debian Buster. Inside

Hello world in AAarch64 Debian Buster

I have a raspberry pi 3B+ running raspbian stretch 32-bit with a containerised guest o/s inside it using systemd-nspawn, the guest o/s being AAarch64 Debian Buster. Inside AAarch64 Debian Buster, I run the following from the shell and get an error from the gdc compiler:

Trying to build GDC from sources (New fool - please be kind)

Got as far as downloading a huge .tar.xz file and extracting it, but U just guessed at a version of gcc sources to ftp-fetch in the first place. I have a gcc-7.3.0 folder now. Is that the correct version number ? Next, the script file setup-gcc.sh comes up with the error message

Re: [Bug 288] strange nonsensical x86-64 code generation with -O3 - rats' nest of useless conditional jumps

On Friday, 23 March 2018 at 22:14:35 UTC, Iain Buclaw wrote: On Friday, 23 March 2018 at 00:39:13 UTC, Cecil Ward wrote: On Thursday, 22 March 2018 at 22:16:16 UTC, Iain Buclaw wrote: https://bugzilla.gdcproject.org/show_bug.cgi?id=288 --- Comment #1 from Iain Buclaw

Re: [Bug 288] strange nonsensical x86-64 code generation with -O3 - rats' nest of useless conditional jumps

On Thursday, 22 March 2018 at 22:16:16 UTC, Iain Buclaw wrote: https://bugzilla.gdcproject.org/show_bug.cgi?id=288 --- Comment #1 from Iain Buclaw --- See the long list of useless conditional jumps towards the end of the first function in the asm output (whose

How to report code generation weirdness

How do I report some extremely weird (useless) code generated by GDC when the -O3 option is used? (bizarre rats’ nest of conditional jumps). [I am an experienced professional asm programmer, now retired.] The D source is short, fortunately. The asm output I am looking at is seen through the