https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100912
--- Comment #10 from Qiu Chaofan ---
Hi, does GCC plan to switch to IEEE-quad as default `long double` semantics (or
at least fully support it but under an option)? If so, I guess this should be a
blocker.
If GCC 12 supports it well, other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100912
--- Comment #9 from Qiu Chaofan ---
I also get following 'symbol not found' error for following case (under
-mabi=ieeelongdouble): undefined reference to
`std::__gnu_cxx11_ieee128::money_get > >::money_get(unsigned long)'
Maybe related?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100912
--- Comment #8 from Qiu Chaofan ---
> Looks like we need two different versions of that symbol, with different
> mangled names.
Yes, I did a little hack: adding another symbol `__convert_from_v_ieee128`
(guarded under macro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100912
--- Comment #6 from Qiu Chaofan ---
By changing the order of linked objects (move .libs/compatibility-ldbl.o
.libs/compatibility-ldbl-alt128.o .libs/compatibility-ldbl-alt128-cxx11.o after
the series of convenience archives), the result under
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100912
Qiu Chaofan changed:
What|Removed |Added
CC||qiu.chaofan at outlook dot com
---
