This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128
- From: "pbristow at hetp dot u-net.com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 02 Mar 2014 10:41:15 +0000
- Subject: [Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128
- Auto-submitted: auto-generated
- References: <bug-43622-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
Paul A. Bristow <pbristow at hetp dot u-net.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pbristow at hetp dot u-net.com
--- Comment #12 from Paul A. Bristow <pbristow at hetp dot u-net.com> ---
This still exists at 4.8.2 and is a *showstopper* for running the Boost.Math
library at all the available precisions, up to 128-bit precision where
available.
typeid(type).name() fails with:
undefined reference to `typeinfo for __float128'
We can check that the library seems to work OK by ugly hacking of error
handling and a few examples of test code (out of the hundreds of tests), but we
absolutely need this before it can be fully tested at 128-bit precision and
released.
Getting this library to pass is part of a demonstration of the proposed C++ and
C library additions by Christopher Kormanyos and John Maddock
Floating-Point Typedefs Having Specified Widths - N3626
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3626.pdf
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1703.pdf
Everything is working to provide full C++ 128-bit floating-point - apart from
this :-(
So we are very keen to have a fix.