On Fri, 16 Jan 2026 at 13:10, Jakub Jelinek <[email protected]> wrote: > > On Fri, Jan 16, 2026 at 02:07:10PM +0100, Richard Biener wrote: > > One might also be able to arrange for int8_t to be mangled the same > > as 'char' even when 'signed char' to avoid the ABI change (but retain > > some of the issues). I'd probably follow what the vendor does, thus > > Studio 12.6 CC, inter-operability with the "platform default" would be > > my priority, and see to have work arounds for the fallout that happens > > elsewhere ... Does Oracle acknowledge the issue and plan to fix > > in a similar manner? > > I don't think such mangling change is feasible, strip_typedefs is called all > over the place, so whether it was originally int8_t or signed char will be > lost in many cases. And changing mangling of signed char would be even much > more significant change (and problematic, because one can overload on char > vs. signed char).
Yes, it would mean that you could overload at the C++ syntax level, but then you would get duplicate definitions at the ELF symbol level.
