jimzah/zig
1
0
Fork 0
mirror of https://github.com/ziglang/zig.git synced 2024-11-28 08:02:32 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
fd9db4962c
zig/lib/compiler_rt/truncsfhf2.zig

26 lines
863 B
Zig
Raw Normal View History

compiler-rt: break up functions even more The purpose of this branch is to switch to using an object file for each independent function, in order to make linking simpler - instead of relying on `-ffunction-sections` and `--gc-sections`, which involves the linker doing the work of linking everything and then undoing work via garbage collection, this will allow the linker to only include the compilation units that are depended on in the first place. This commit makes progress towards that goal.
2022-06-16 07:09:56 +01:00
const common = @import("./common.zig");
const truncf = @import("./truncf.zig").truncf;
pub const panic = common.panic;
comptime {
compiler-rt: fix logic for choosing `__gnu_{f2h,h2f}_ieee` wasm32-wasi-musl wants the standard symbol names however Linux requires the `__gnu_*` flavors. I did not find any authoritative source on what decides which symbol flavors to use. If we run into more trouble in the future we can go back to having both.
2022-06-18 03:25:06 +01:00
if (common.gnu_f16_abi) {
compiler-rt: Set the symbol visibility When we're compiling compiler_rt for any WebAssembly target, we do not want to expose all the compiler-rt functions to the host runtime. By setting the visibility of all exports to `hidden`, we allow the linker to resolve the symbols during linktime, while not expose the functions to the host runtime. This also means the linker can properly garbage collect any compiler-rt function that does not get resolved. The symbol visibility for all target remains the same as before: `default`.
2022-12-28 13:57:17 +00:00
@export(__gnu_f2h_ieee, .{ .name = "__gnu_f2h_ieee", .linkage = common.linkage, .visibility = common.visibility });
compiler-rt: break up functions even more The purpose of this branch is to switch to using an object file for each independent function, in order to make linking simpler - instead of relying on `-ffunction-sections` and `--gc-sections`, which involves the linker doing the work of linking everything and then undoing work via garbage collection, this will allow the linker to only include the compilation units that are depended on in the first place. This commit makes progress towards that goal.
2022-06-16 07:09:56 +01:00
} else if (common.want_aeabi) {
compiler-rt: Set the symbol visibility When we're compiling compiler_rt for any WebAssembly target, we do not want to expose all the compiler-rt functions to the host runtime. By setting the visibility of all exports to `hidden`, we allow the linker to resolve the symbols during linktime, while not expose the functions to the host runtime. This also means the linker can properly garbage collect any compiler-rt function that does not get resolved. The symbol visibility for all target remains the same as before: `default`.
2022-12-28 13:57:17 +00:00
@export(__aeabi_f2h, .{ .name = "__aeabi_f2h", .linkage = common.linkage, .visibility = common.visibility });
compiler-rt: break up functions even more The purpose of this branch is to switch to using an object file for each independent function, in order to make linking simpler - instead of relying on `-ffunction-sections` and `--gc-sections`, which involves the linker doing the work of linking everything and then undoing work via garbage collection, this will allow the linker to only include the compilation units that are depended on in the first place. This commit makes progress towards that goal.
2022-06-16 07:09:56 +01:00
}
compiler-rt: Set the symbol visibility When we're compiling compiler_rt for any WebAssembly target, we do not want to expose all the compiler-rt functions to the host runtime. By setting the visibility of all exports to `hidden`, we allow the linker to resolve the symbols during linktime, while not expose the functions to the host runtime. This also means the linker can properly garbage collect any compiler-rt function that does not get resolved. The symbol visibility for all target remains the same as before: `default`.
2022-12-28 13:57:17 +00:00
@export(__truncsfhf2, .{ .name = "__truncsfhf2", .linkage = common.linkage, .visibility = common.visibility });
compiler-rt: break up functions even more The purpose of this branch is to switch to using an object file for each independent function, in order to make linking simpler - instead of relying on `-ffunction-sections` and `--gc-sections`, which involves the linker doing the work of linking everything and then undoing work via garbage collection, this will allow the linker to only include the compilation units that are depended on in the first place. This commit makes progress towards that goal.
2022-06-16 07:09:56 +01:00
}
compiler_rt: change the abi of f16 on mac to depend on the other type
2023-03-28 02:32:37 +01:00
pub fn __truncsfhf2(a: f32) callconv(.C) common.F16T(f32) {
compiler_rt: fight off `@as` invasion Importantly, fixes incorrectly annotated types in `__aeabi_?2h`.
2023-08-19 08:32:47 +01:00
return @bitCast(truncf(f16, f32, a));
compiler-rt: break up functions even more The purpose of this branch is to switch to using an object file for each independent function, in order to make linking simpler - instead of relying on `-ffunction-sections` and `--gc-sections`, which involves the linker doing the work of linking everything and then undoing work via garbage collection, this will allow the linker to only include the compilation units that are depended on in the first place. This commit makes progress towards that goal.
2022-06-16 07:09:56 +01:00
}
compiler_rt: change the abi of f16 on mac to depend on the other type
2023-03-28 02:32:37 +01:00
fn __gnu_f2h_ieee(a: f32) callconv(.C) common.F16T(f32) {
compiler_rt: fight off `@as` invasion Importantly, fixes incorrectly annotated types in `__aeabi_?2h`.
2023-08-19 08:32:47 +01:00
return @bitCast(truncf(f16, f32, a));
compiler_rt: avoid using weak aliases This is a partial revert of 0d533433e21621177fb291e2a4901bee11834501, which regressed this behavior. The idea here is to avoid aliases, which happens when the same function is exported with multiple names. The problem with aliases is that weak aliases don't seem to work, causing symbol collisions when multiple of the same symbol are provided, despite the desired behavior that weak symbols are overridden. In this case we export redundant functions with different names. Thanks to -ffunction-sections, the unused functions will be garbage-collected at link time. This leaves us with the best of both worlds: Zig's compiler-rt will provide both sets of symbols, and it will be binary-compatible with different compilers that expect different names, while still resulting in binaries without garbage.
2022-12-05 21:52:21 +00:00
}
compiler-rt: break up functions even more The purpose of this branch is to switch to using an object file for each independent function, in order to make linking simpler - instead of relying on `-ffunction-sections` and `--gc-sections`, which involves the linker doing the work of linking everything and then undoing work via garbage collection, this will allow the linker to only include the compilation units that are depended on in the first place. This commit makes progress towards that goal.
2022-06-16 07:09:56 +01:00
fn __aeabi_f2h(a: f32) callconv(.AAPCS) u16 {
compiler_rt: fight off `@as` invasion Importantly, fixes incorrectly annotated types in `__aeabi_?2h`.
2023-08-19 08:32:47 +01:00
return @bitCast(truncf(f16, f32, a));
compiler-rt: break up functions even more The purpose of this branch is to switch to using an object file for each independent function, in order to make linking simpler - instead of relying on `-ffunction-sections` and `--gc-sections`, which involves the linker doing the work of linking everything and then undoing work via garbage collection, this will allow the linker to only include the compilation units that are depended on in the first place. This commit makes progress towards that goal.
2022-06-16 07:09:56 +01:00
}
Reference in New Issue Copy Permalink