This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [trans-mem][build] Hack around top-level Makefile libstdc++ breakage
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 4 Nov 2011 09:12:26 -0700
- Subject: Re: [trans-mem][build] Hack around top-level Makefile libstdc++ breakage
- References: <4EB37ECE.4010807@redhat.com>
On Thu, Nov 3, 2011 at 10:57 PM, Richard Henderson <rth@redhat.com> wrote:
> We currently have a problem building libitm because it uses the libstdc++
> header <type_traits>, and the toplevel Makefile passes a single set of
> include paths for all multilibs. ?In the recent merges from mainline, we
> brought in changes to that header that reference __int128_t.
>
> Building for x86_64, we detect that __int128_t is supported for the main
> multilib, but when it comes to building the -m32 multilib we do not
> support that type. ?With the incorrect include path, we read the wrong
> <bits/c++config> file, which leads us to attempt to use __int128_t in
> the -m32 libitm multlib, which of course fails.
>
I believe that C++ tests pick the correct bits/c++config for -m32. Can't
libitm do something similar?
--
H.J.