Displaying 3 results from an estimated 3 matches for "d_glibcxx_use_cxx11_abi".
2016 May 04
2
Clang 3.8 and gcc 5.2 has difference in symbol names
...th c++11 support has added this special behavior due to which
symbol name contains B5cxx11. Hence, I tried building LLVM/clang with
-std=c++14 support. But no luck.
Even if I provide -std=c++14 while compiling this source file using
clang++, the result remained same.
I tried setting -D_GLIBCXX_USE_CXX11_ABI=0 flag while compiling my
application using gcc. This approach atleast gave me some success.
Symbols generated for my source file after using flag were same as that
of clang++ (i.e. without B5cxx11). But later my application failed at
linking step for some undefined references - some of...
2016 Sep 27
2
(Thin)LTO llvm build
...CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
This is the same way Fedora or Arch linux would build clang, or any
other usual package for that matter.
The only uncommon thing I set is the macro -D_GLIBCXX_USE_CXX11_ABI=0,
which I use to avoid C++11 ABI chaos since g++5.x, although it's
probably safe to drop by now, especially when CXX=clang++. That's
g++-specific, so is irrelevant to the issue at hand.
> I wonder if there is a bug that was fixed. I have bootstrapped with
> ThinLTO with the 3.9 comp...
2016 Sep 27
2
(Thin)LTO llvm build
On Tue, Sep 27, 2016 at 6:33 PM, Teresa Johnson <tejohnson at google.com> wrote:
>
> I can't reproduce the failure. I am building with a clang built
> Release from recent source as my stage-1 bootstrap compiler:
> clang version 4.0.0 (trunk 282322) (llvm/trunk 282341)
The clang I use was built from the 3.9 release branch:
clang version 3.9.1 (branches/release_39