Alex Rønne Petersen

> Is there something I can do in the build.zig to hide the stderr output when the test passes? You can capture the output from the build script, e.g. by...

I guess you could just change the test's `build.zig` to ignore the standard target option and instead build & run for a predefined set of targets? `test/llvm_targets.zig` is a good...

> Two unrequested changes: (1) I got suspicious that the Darwin-aarch64 alignment hack-around in the test's signal handler was influencing other platforms, so I re-worked the code to more clearly...

Have you tried experimenting with this directive? https://sourceware.org/binutils/docs/as/CFI-directives.html#g_t_002ecfi_005fsignal_005fframe

Also this definitely needs a rebase after #24960.

It seems like we also have * `cosf` * `sincos` (includes `sincosl`?) * `sincosf` * `sinf` * `tanf` in `lib/libc/mingw`.

> Do I need to make sure that the behavior of compiler_rt's `sin` function and MinGW's `sin` function match? I don't think so. musl tends to be pretty good about...

No worries, I'm not calling dibs or anything. :slightly_smiling_face:

Very strongly suspect this is a duplicate of #16331, or closely related.

Closing as duplicate of #16331, which also has a workaround.