Hi! On Fri, 2023-05-26 15:33:00 +0200, Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost> wrote: > On Fri, 2023-05-26 14:13:25 +0100, David Brownlee <abs%absd.org@localhost> wrote: > > > Presumably it might be possible to add in alpha using a similar > > pattern? :) (*Not* trying for "Oh, that is cool. Now You Must This As > > Well") > > The code for building the VAX compiler for CE is in > https://github.com/compiler-explorer/gcc-cross-builder.git, see > ./build/build-vax-netbsd.sh . It's quite trivial code, given that > NetBSD's build.sh is easily preparing a working (cross-)compiler for > supported targets. If you open a ticket with CE and maybe supply > either a second script (along with the above mentioned > build-vax-netbsd.sh), or a common script to be called for VAX and > Alpha, I guess we'll easily see an Alpha compiler soon. I gave it another thought. Depending on what you're aiming for, there's two routes for Alpha. You could, as I described above, request a NetBSD-based compiler and (as a nice guy) also supply a script, much like that one for VAX. However, their usual way to gain a GCC variant is to use Crosstool-NG. So an even easier route (if alpha-elf or alpha-linux is good enough) would be to just supply a CT-NG configuration. As I see in my CI builder (http://toolchain.lug-owl.de/laminar/jobs), there are already two alpha configurations (alphaev56-unknown-linux-gnu and alphaev67-unknown-linux-gnu) which work fine. MfG, JBG --
Attachment:
signature.asc
Description: PGP signature