From: "Tulio Magno Quites Machado Filho" <tuliom@linux.vnet.ibm.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
libstdc++ <libstdc++@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
wschmidt@linux.vnet.ibm.com,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCHv2] PR libstdc++/84654 Do not use __float128 if it is disabled by the compiler
Date: Mon, 26 Mar 2018 15:23:00 -0000 [thread overview]
Message-ID: <87a7uueueo.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180312190224.19137-1-tuliom@linux.vnet.ibm.com>
Ping?
Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com> writes:
> Changes since v1:
> - Completely rewrite of the patch to set ENABLE_FLOAT128 at libstdc++
> build time and undef _GLIBCXX_USE_FLOAT128 when building user code.
>
> --- 8< ---
>
> In order to use __float128 in C++ it's necessary to check if the
> compiler enabled its support too when building user code.
> This patch changes the behavior at libstdc++ build by setting
> ENABLE_FLOAT128, which is used to set the value of the exported macro
> _GLIBCXX_USE_FLOAT128.
>
> 2018-03-12 Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
>
> PR libstdc++/84654
> * acinclude.m4: Set ENABLE_FLOAT128 instead of _GLIBCXX_USE_FLOAT128.
> * config.h.in: Remove references to _GLIBCXX_USE_FLOAT128.
> * configure: Regenerate.
> * include/Makefile.am: Replace the value of _GLIBCXX_USE_FLOAT128
> based on ENABLE_FLOAT128.
> * include/Makefile.in: Regenerate.
> * include/bits/c++config: Define _GLIBCXX_USE_FLOAT128.
> [!defined(__FLOAT128__) && !defined(__SIZEOF_FLOAT128__)]: Undefine
> _GLIBCXX_USE_FLOAT128.
--
Tulio Magno
next prev parent reply other threads:[~2018-03-26 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 18:47 [PATCH] " Tulio Magno Quites Machado Filho
2018-03-01 18:54 ` Marc Glisse
2018-03-01 22:04 ` Jonathan Wakely
2018-03-12 19:02 ` [PATCHv2] " Tulio Magno Quites Machado Filho
2018-03-26 15:23 ` Tulio Magno Quites Machado Filho [this message]
2018-05-01 14:34 ` Jonathan Wakely
2018-05-07 20:03 ` Jonathan Wakely
2018-03-01 19:10 ` [PATCH] " Jakub Jelinek
2018-03-01 20:52 ` Jakub Jelinek
2018-03-01 20:56 ` Marc Glisse
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=87a7uueueo.fsf@linux.vnet.ibm.com \
--to=tuliom@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.vnet.ibm.com \
/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).