kikairoya via Cygwin writes: > As a result, Clang and pre-17 GCC are ABI-incompatible with libstdc++ built by > GCC 17 when a __int128 value is returned across the library boundary.
Which means that Cygwin will have a knotty problem on hand when we need to update to gcc-17. How big of a problem that is (i.e. which existing binaries use this return type and need to be rebuilt) I have no idea yet how to figure out. > A change to make Clang compatible with GCC is under review: > > https://github.com/llvm/llvm-project/pull/210358 > > From a Clang perspective, I hope that Cygwin will adopt the new > upstream ABI, since it's difficult to maintain an ABI divergence for Cygwin > alone, given that all of the calling conventions are shared across all > targets. Not anytime soon if we keep switching gcc to a new major version when it reaches x.4… Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
