Re: GDC for ARM MacOS / OSX

2024-08-24 Thread Cecil Ward via D.gnu
On Thursday, 22 August 2024 at 17:34:58 UTC, Iain Buclaw wrote: On Thursday, 22 August 2024 at 16:56:06 UTC, Cecil Ward wrote: If I understand Iain’s reply correctly, the showstopper was lack of support for AArch64 / MacOS in GCC at the time. Has that situation improved by now ? If the situ

GDC for ARM MacOS / OSX

2024-08-22 Thread Cecil Ward via D.gnu
https://forum.dlang.org/post/mjnbswzizylffjyri...@forum.dlang.org On Thursday, 29 June 2023 at 17:16:42 UTC, Cecil Ward wrote: 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 th

Re: GDC for ARM MacOS / OSX

2023-06-29 Thread Cecil Ward via D.gnu
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 avai

GDC for ARM MacOS / OSX

2023-06-28 Thread Cecil Ward via D.gnu
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

2023-06-17 Thread Cecil Ward via D.gnu
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

bug report x86-64 code: je / jbe

2023-06-14 Thread Cecil Ward via D.gnu
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

2023-06-07 Thread Cecil Ward via D.gnu
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

2019-08-27 Thread Cecil Ward via D.gnu
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 program

Re: Hello world in AAarch64 Debian Buster

2019-08-07 Thread Cecil Ward via D.gnu
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 makes

Re: Hello world in AAarch64 Debian Buster

2019-08-06 Thread Cecil Ward via D.gnu
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 A

Hello world in AAarch64 Debian Buster

2019-08-05 Thread Cecil Ward via D.gnu
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: root@debian-buster-64

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

2018-03-25 Thread Cecil Ward via D.gnu
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

2018-03-25 Thread Cecil Ward via D.gnu
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 --- See the long list of

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

2018-03-22 Thread Cecil Ward via D.gnu
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 demangled name is test.t1(unit))

How to report code generation weirdness

2018-03-20 Thread Cecil Ward via D.gnu
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 t