public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/43622] no C++ typeinfo for __float128
Date: Tue, 22 Apr 2014 17:06:00 -0000 [thread overview]
Message-ID: <bug-43622-4-45VcumBktA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43622-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |redi at gcc dot gnu.org
--- Comment #16 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> I guess #c4 patch will break ppc/s390 etc.
> config/os/gnu-linux/ldbl-extra.ver already has:
> CXXABI_LDBL_1.3 {
> _ZT[IS]g;
> _ZT[IS]Pg;
> _ZT[IS]PKg;
> };
>
> So, IMNSHO you don't want to add something like that to gnu.ver, but have
> a special *.ver file for those 3 targets (i?86/x86_64/ia64) that have
> __float128.
Er, oups, I was going to close the bug, but apparently I overlooked this
comment when writing the patch, sorry :-(
Should I revert right away?
It looks like I need to create a file config/?/?/float128.ver and find the
right incantation in configure to add it to port_specific_symbol_files for
those 3 targets?
next prev parent reply other threads:[~2014-04-22 17:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43622-4@http.gcc.gnu.org/bugzilla/>
2011-02-24 8:25 ` [Bug libstdc++/43622] no C++ typeinfo for __float128 and __int128 bkoz at gcc dot gnu.org
2011-02-24 16:04 ` joseph at codesourcery dot com
2011-02-24 18:59 ` bkoz at gcc dot gnu.org
2011-02-24 19:06 ` bkoz at gcc dot gnu.org
2011-02-24 19:28 ` bkoz at gcc dot gnu.org
2011-02-24 19:42 ` jakub at gcc dot gnu.org
2011-02-24 20:14 ` bkoz at gcc dot gnu.org
2011-03-25 19:58 ` jakub at gcc dot gnu.org
2011-04-14 15:56 ` planet36 at gmail dot com
2011-04-28 16:15 ` rguenth at gcc dot gnu.org
2011-09-25 15:06 ` paolo.carlini at oracle dot com
2012-10-21 22:06 ` planet36 at gmail dot com
2014-03-02 10:41 ` pbristow at hetp dot u-net.com
2014-03-02 12:15 ` glisse at gcc dot gnu.org
2014-03-02 16:11 ` [Bug libstdc++/43622] no C++ typeinfo for __float128 glisse at gcc dot gnu.org
2014-04-22 16:45 ` glisse at gcc dot gnu.org
2014-04-22 17:06 ` glisse at gcc dot gnu.org [this message]
2014-04-22 17:25 ` glisse at gcc dot gnu.org
2014-04-22 17:55 ` glisse at gcc dot gnu.org
2014-11-18 20:21 ` glisse at gcc dot gnu.org
2014-11-18 20:42 ` glisse at gcc dot gnu.org
2014-11-18 23:50 ` joseph at codesourcery dot com
2014-11-20 17:12 ` john at johnmaddock dot co.uk
2014-11-21 12:18 ` john at johnmaddock dot co.uk
2015-04-04 13:36 ` [Bug libstdc++/43622] Incomplete C++ library support " glisse at gcc dot gnu.org
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2023-05-16 18:19 ` pinskia at gcc dot gnu.org
2023-05-16 18:47 ` redi at gcc dot gnu.org
2023-05-16 18:49 ` redi at gcc dot gnu.org
2023-05-16 19:33 ` joseph at codesourcery dot com
2023-05-16 19:43 ` redi at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-43622-4-45VcumBktA@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).