Open bnoordhuis opened 3 weeks ago
Another option would be to pile the affected clang versions onto the ifdef mixture. According to the minimal repro this seems specific to clang 15 (doesn't reproduce on neither clang 14.0.0 nor 16.0.0)
Actually I remember we are using clang 15 for macOS in the canary CI? @targos
There's nothing special about the canary CI. It's using the same machines and config as main
According to https://en.wikipedia.org/wiki/Xcode#Xcode_11.0_-_14.x_(since_SwiftUI_framework)_2, clang 15 wasn't included for a long time in Xcode (it's the LLVM column):
I've seen this bug with both clang 14 and 15. What do our buildbots use? 16?
Forgot to mention, I have a patch ready for upstreaming but I'd like to narrow down the range of broken clangs.
In Jenkins, the buildbots use Clang 12 In GitHub actions, it seems to be Clang 15.
(on macOS)
on Linux, I think we only use Clang in GitHub actions, and it's on version 18.
Like https://github.com/nodejs/node/issues/53633 which was for gcc 12 and fixed in commit f4a7ac5e1842c0f4629a0bebfda38f2502a2ee41 but with clang 15.0.7 on x86_64 linux I get the exact same build error:
Maybe just remove that ASSERT_TRIVIALLY_COPYABLE? Upstream already tests for correctness and to us it's just a recurring source of build breakage.