On Sat, Jun 7, 2025 at 6:47 AM Andres Freund <and...@anarazel.de> wrote: > On 2025-06-06 14:03:12 +0300, Konstantin Knizhnik wrote: > > There is really essential difference in code generated by clang 15 (working) > > and 16 (not working). > > There also are code gen differences between upstream clang 17 and apple's > clang, which is based on llvm 17 as well (I've updated the toolchain, it > repros with that as well).
Just for the record, Apple clang 17 (self-reported clobbered version) is said to be based on LLVM 19[1]. For a long time it was off by one but tada now it's apparently two. Might be relevant if people are comparing generated code up that close.... . o O (I wonder if one could corroborate that by running "strings" on upstream clang binaries (as compiled by MacPorts/whatever) for each major version and finding new strings, ie strings that don't appear in earlier major versions, and then seeing which ones are present in Apple's clang binaries... What a silly problem.) [1] https://en.wikipedia.org/wiki/Xcode#Xcode_15.0_-_16.x_(since_visionOS_support)
