aboutsummaryrefslogtreecommitdiff
path: root/src/target.zig
diff options
context:
space:
mode:
authorAlex Rønne Petersen <alex@alexrp.com>2024-08-02 08:13:00 +0200
committerAlex Rønne Petersen <alex@alexrp.com>2024-08-02 09:54:08 +0200
commit635a3d87de03193f28bb840957e387981365566f (patch)
tree7d1db2356a4ee9ca7c88ed57e068840a941090e7 /src/target.zig
parent3c2733de6e20926b5113236296177e1b2a576423 (diff)
downloadzig-635a3d87de03193f28bb840957e387981365566f.tar.gz
zig-635a3d87de03193f28bb840957e387981365566f.zip
glibc: Change riscv32-linux-gnuilp32 target triple to riscv32-linux-gnu.
This target triple was weird on multiple levels: * The `ilp32` ABI is the soft float ABI. This is not the main ABI we want to support on RISC-V; rather, we want `ilp32d`. * `gnuilp32` is a bespoke tag that was introduced in Zig. The rest of the world just uses `gnu` for RISC-V target triples. * `gnu_ilp32` is already the name of an ILP32 ABI used on AArch64. `gnuilp32` is too easy to confuse with this. * We don't use this convention for `riscv64-linux-gnu`. * Supporting all RISC-V ABIs with this convention will result in combinatorial explosion; see #20690.
Diffstat (limited to 'src/target.zig')
-rw-r--r--src/target.zig1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/target.zig b/src/target.zig
index 768e4d957e..6cd5967d0e 100644
--- a/src/target.zig
+++ b/src/target.zig
@@ -369,7 +369,6 @@ pub fn addrSpaceCastIsValid(
pub fn llvmMachineAbi(target: std.Target) ?[:0]const u8 {
const have_float = switch (target.abi) {
- .gnuilp32 => return "ilp32",
.gnueabihf, .musleabihf, .eabihf => true,
else => false,
};