On 4/27/14, Markus Trippelsdorf wrote:> On 2014.04.27 at 16:18 +0200, Tuncer Ayaz wrote:
> > Using gcc 4.9 to build the llvm 3.4 branch fails with the
> > following error:
> >
> > llvm[1]: Compiling APFloat.cpp for Release build
> > [...]
> > /usr/[...]/include/c++/4.9.0/cstddef:51:11:
> > error: no member named 'max_align_t' in the global namespace
> > using ::max_align_t;
> > ~~^
> >
> > gcc 4.8.2's caused no such issue, so it must be a change in
> > 4.9.0/cstddef.
> >
> > To be clear, I have no idea who's at fault (gcc 4.9.0 header or
> > llvm sources), assuming any code is to be blamed (at all).
>
> You can simply wrap it with #ifndef:
>
> namespace std
> {
> // We handle size_t, ptrdiff_t, and nullptr_t in c++config.h.
> #ifndef __clang__
> using ::max_align_t;
> #endif
> }
> #endif
Yeah, but are you sure the bug is in libstdc++ and has to be fixed in
gcc upstream? I mean, would it be the wrong choice to include a fix in
the next llvm 3.4 release?