This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCHv2] PR libstdc++/84654 Do not use __float128 if it is disabled by the compiler
- From: Jonathan Wakely <jwakely at redhat dot com>
- To: Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>
- Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, libstdc++ <libstdc++ at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>, wschmidt at linux dot vnet dot ibm dot com, Segher Boessenkool <segher at kernel dot crashing dot org>
- Date: Tue, 1 May 2018 15:34:31 +0100
- Subject: Re: [PATCHv2] PR libstdc++/84654 Do not use __float128 if it is disabled by the compiler
- References: <CAH6eHdTZ4fTB1A6BDG1Xn1Y78c3SVFEP70yEUXLNfBkNn62+1A@mail.gmail.com> <20180312190224.19137-1-tuliom@linux.vnet.ibm.com>
On 12/03/18 16:02 -0300, Tulio Magno Quites Machado Filho wrote:
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.
Now that we're in stage 1 we can make this change. The patch looks
right so I'll go ahead and commit it to trunk (it shouldn't interfere
with testing any last-minute fixes needed for gcc-8).
Thanks for fixing this, Tulio.