Jakub Konka

> > I'm surprised by the linker errors. Are we perhaps missing custom re-exports with renames of globals in compiler-rt for some 32bit targets? > > The problem is that...

> Eugh... Intel x86-64 loves the new inline assembly, but AMD hates it: > > ``` > intrinsics: 66870 us (1568.08 MB/s) > inline asm: 251760 us (416.50 MB/s) >...

> > What about arm64? Comparable, or ahead, or behind? If the latter, that's bad timing as I wanted to start testing it out in zld repo. > > arm64...

Is there any trick to building any of this locally? On my M1Pro I am getting: ``` error: :2:1: instruction requires: sha2 sha256h.4s v2, v1, v3 ```

> @kubkon what does `zig build-exe --show-builtin` output for you? ``` pub const cpu: std.Target.Cpu = .{ .arch = .aarch64, .model = &std.Target.aarch64.cpu.apple_a14, .features = std.Target.aarch64.featureSet(&[_]std.Target.aarch64.Feature{ .aes, .aggressive_fma, .alternate_sextload_cvt_f32_pattern, .altnzcv,...

Here's a dirty hack until I thoroughly investigate what is up with `x86_64` dropping `_tls_index` symbol, and confirm it doesn't happen on `aarch64`: ```diff diff --git a/src/Compilation.zig b/src/Compilation.zig index 958aac5e1..9e62c5f24...

@i0ntempest could you paste your `cmake` invocation in full, and also could you check if this still happens for you with latest master?

@i0ntempest is the issue still there?

> Yes, it's caused by [this patch](https://github.com/macports/macports-ports/blob/e8ee22994285a56f684af1ddf7841051378f1410/lang/llvm-13/files/0019-10.6-and-less-use-emulated-TLS-before-10.7.patch) we use for our clang compilers, though we could not figure out exactly why because it shouldn't change anything on new systems, and...

> > > Yes, it's caused by [this patch](https://github.com/macports/macports-ports/blob/e8ee22994285a56f684af1ddf7841051378f1410/lang/llvm-13/files/0019-10.6-and-less-use-emulated-TLS-before-10.7.patch) we use for our clang compilers, though we could not figure out exactly why because it shouldn't change anything on new...