Martin Kinkelin

@thewilsonator proposed this 7 years ago in https://forum.dlang.org/thread/[email protected] - for dlang in general, no LDC-specific language extension. I don't know how that thread ended. And https://forum.dlang.org/thread/[email protected] proposed skipping codegen for...

This would be a manageable CI addition if it weren't for the fact that we'd need a musl-LLVM for linking too, so another CI addition to our LLVM repo.

Yeah, you'll need cross-compiled druntime/Phobos too and tell LDC to use the musl-gcc/clang for linking. See https://wiki.dlang.org/Cross-compiling_with_LDC.

The example cmdlines in https://wiki.dlang.org/Building_LDC_runtime_libraries indicate that that's not really an option IMO. Once we have something like an `ldc-add-target` tool which downloads & extracts a prebuilt archive and sets...

Travis is too slow, the only feasible option is Azure Pipelines, which generates all packages (LLVM + LDC) except for the AArch64 Linux ones. LLVM would be a prerequisite (our...

I've already dismissed that one, as there's no real advantage over Azure Pipelines AFAICT (but e.g. only half as many CPU cores for the Mac machines).

MIPS is a bit weird with its ABIs AFAICT; looks like our default is off: https://github.com/ldc-developers/ldc/blob/48c1dff0466f5231619356ae33ef1a181888a1ff/driver/targetmachine.cpp#L154-L156 ``` $ ldc2 -c ../hello.d -mtriple=mips64el-linux -mabi=n64 $ file hello.o hello.o: ELF 64-bit LSB...

Judging from the clang default, it seems so. Looks like `n32` was intended for the 32-bit MIPS targets (which have no default ABI currently), i.e., `llvm::Triple::mips[el]`.

Yep.

@aneves: Finally ready after 8 months! - The unrelated last commit fixes CI (for master), while at it - GitHub Actions removed the used macos-12 image. A quick merge would...