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, 18 Nov 2014 20:21:00 -0000	[thread overview]
Message-ID: <bug-43622-4-wWbmeEbI72@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43622-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622

--- Comment #21 from Marc Glisse <glisse at gcc dot gnu.org> ---
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  <marc.glisse@inria.fr>

    PR libstdc++/43622
gcc/cp/
    * rtti.c (emit_support_tinfos): Handle __float128.
libstdc++-v3/
    * config/abi/pre/float128.ver: New file.
    * configure.ac: Use float128.ver when relevant.
    * configure: Regenerate.
    * testsuite/util/testsuite_abi.cc (check_version): Accept new
    CXXABI_FLOAT128 version.


Added:
    trunk/libstdc++-v3/config/abi/pre/float128.ver
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/rtti.c
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/configure
    trunk/libstdc++-v3/configure.ac
    trunk/libstdc++-v3/testsuite/util/testsuite_abi.cc


  parent reply	other threads:[~2014-11-18 20:21 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
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 [this message]
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-wWbmeEbI72@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).