On Tue, Dec 06, 2022 at 05:36:54PM +0800, Kewen.Lin wrote: > Hi Mike, > > Thanks for fixing this! > > Could you help to elaborate why we need to disable it during libgcc building?
When you are building libgcc, you are building the __mulkc3, __divkc3 functions. The mapping in the compiler interferes with those functions, because at the moment, libgcc uses an alternate IEEE 128-bit type. I have a patch for making libgcc use the 'right' type that I haven't submitted yet. This is because the more general fix that these 3 patches do impacts other functions (due to __float128 and _Float128 being different in the current compiler when -mabi=ieeelongdouble). -- Michael Meissner, IBM PO Box 98, Ayer, Massachusetts, USA, 01432 email: meiss...@linux.ibm.com
