[Bug libstdc++/43622] no C++ typeinfo for __float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #26 from John Maddock --- (In reply to jos...@codesourcery.com from comment #25) > On Thu, 20 Nov 2014, john at johnmaddock dot co.uk wrote: > > > While we're opening cans of worms intmax_t should clearly be __int128... > > just

[Bug libstdc++/43622] no C++ typeinfo for __float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #25 from joseph at codesourcery dot com --- On Thu, 20 Nov 2014, john at johnmaddock dot co.uk wrote: > While we're opening cans of worms intmax_t should clearly be __int128... > just saying! Existing ABIs where intmax_t in libc

[Bug libstdc++/43622] no C++ typeinfo for __float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 John Maddock changed: What|Removed |Added CC||john at johnmaddock dot co.uk --- Comment

[Bug libstdc++/43622] no C++ typeinfo for __float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #23 from joseph at codesourcery dot com --- On Tue, 18 Nov 2014, glisse at gcc dot gnu.org wrote: > __float128 is still missing a specialization of numeric_limits. Fully supporting an extended type (whether floating-point, or one li

[Bug libstdc++/43622] no C++ typeinfo for __float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #22 from Marc Glisse --- __float128 is still missing a specialization of numeric_limits.

[Bug libstdc++/43622] no C++ typeinfo for __float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #21 from Marc Glisse --- Author: glisse Date: Tue Nov 18 20:20:53 2014 New Revision: 217735 URL: https://gcc.gnu.org/viewcvs?rev=217735&root=gcc&view=rev Log: 2014-11-18 Marc Glisse PR libstdc++/43622 gcc/cp/ * rtti.c (em

[Bug libstdc++/43622] no C++ typeinfo for __float128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #20 from Marc Glisse --- Author: glisse Date: Thu Apr 24 13:58:36 2014 New Revision: 209748 URL: http://gcc.gnu.org/viewcvs?rev=209748&root=gcc&view=rev Log: 2014-04-24 Marc Glisse PR libstdc++/43622 gcc/cp/ * rtti.c (emit

[Bug libstdc++/43622] no C++ typeinfo for __float128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #19 from Marc Glisse --- Created attachment 32654 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32654&action=edit potential export fix I am currently testing the attached.

[Bug libstdc++/43622] no C++ typeinfo for __float128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Marc Glisse changed: What|Removed |Added CC||glisse at gcc dot gnu.org --- Comment #18 f

[Bug libstdc++/43622] no C++ typeinfo for __float128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #17 from Jonathan Wakely --- (In reply to Marc Glisse from comment #16) > Should I revert right away? If it doesn't break bootstrap for the ldbl targets (only causes test failures) then I would say reverting it is not necessary if you

[Bug libstdc++/43622] no C++ typeinfo for __float128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Marc Glisse changed: What|Removed |Added CC||redi at gcc dot gnu.org --- Comment #16 fro

[Bug libstdc++/43622] no C++ typeinfo for __float128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #15 from Marc Glisse --- Author: glisse Date: Tue Apr 22 16:44:46 2014 New Revision: 209652 URL: http://gcc.gnu.org/viewcvs?rev=209652&root=gcc&view=rev Log: 2014-04-22 Marc Glisse PR libstdc++/43622 gcc/c-family/ * c-comm

[Bug libstdc++/43622] no C++ typeinfo for __float128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Marc Glisse changed: What|Removed |Added Summary|no C++ typeinfo for |no C++ typeinfo for |__fl

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #13 from Marc Glisse --- It looks like emit_support_tinfos (rtti.c) should go through registered_builtin_types (hidden in c-common.c) in addition to the hardcoded fundamentals list.

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Paul A. Bristow changed: What|Removed |Added CC||pbristow at hetp dot u-net.com --- Comm

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #11 from Steve Ward 2012-10-21 22:05:35 UTC --- This problem still exists in g++ 4.7.2.

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Paolo Carlini changed: What|Removed |Added CC||john.salmon at deshaw dot

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Richard Guenther changed: What|Removed |Added Target Milestone|4.6.1 |---

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #9 from Steve Ward 2011-04-14 15:56:12 UTC --- Created attachment 23982 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23982 This test-case shows how typeinfo for non-complex 128-bit types DOES NOT work, but typeinfo for complex

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Jakub Jelinek changed: What|Removed |Added Target Milestone|4.6.0 |4.6.1 --- Comment #8 from Jakub Jelinek

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #7 from Benjamin Kosnik 2011-02-24 19:28:02 UTC --- ack, I mis-read rtti.c, these are the decimal exports, ie decimal128 not float128. Jakub you are correct these are exports as LD symbols via ld versioning via inclusion. I missed

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #6 f

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #5 from Benjamin Kosnik 2011-02-24 19:09:33 UTC --- RE comment 2. Yes, agreed full support is a ways off. However, typeinfo support is ostensibly already there, just not emitted. This is a bug, and not something users can work arou

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #4 from Benjamin Kosnik 2011-02-24 18:54:06 UTC --- Created attachment 23457 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23457 typeinfo exports for float128

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #3 from Benjamin Kosnik 2011-02-24 18:53:08 UTC --- Expecting this as exported as fundamental_type_info, see in emit_support_tinfos via rtti.c:1461: static tree *const fundamentals[] = { &void_type_node, &boolean_type_no

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 --- Comment #2 from joseph at codesourcery dot com 2011-02-24 15:23:33 UTC --- This seems related to bug 40855. See also and the rest of that thread. libstdc++ support for extended inte

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622 Benjamin Kosnik changed: What|Removed |Added CC||bkoz at gcc dot gnu.org Assigne

[Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128

-- paolo dot carlini at oracle dot com changed: What|Removed |Added Severity|normal |enhancement http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622