Issue metadata
Sign in to add a comment
|
Link Chrome on Linux with libc++, statically, with LTO |
||||||||||||||||||||||
Issue descriptionCurrently, we have a lot of types in the standard C++ library excluded from CFI, because they are in the shared libstdc++ library. We need to link libc++ statically so that these types are covered by CFI too. Realistically, this depends on implementing more devirtualization techniques than we have now, as I expect the standard library to have a number of cases of the code where CFI imposes a huge tax (and that can be avoided with better optimizations)
,
Feb 28 2017
xyzzyz@, do you have any plans here?
,
Feb 28 2017
I think the plan is to follow through with the original approach, that is, ship precompiled static libcxx.a and libcxxabi.a libraries with Clang. I've been pretty busy recently though, unfortunately.
,
Feb 28 2017
>> ship precompiled static libcxx.a and libcxxabi.a That won't work for our use case where we need to build chrome and libcxx*.a together with LTO. >> I've been pretty busy recently though, unfortunately. :(
,
Feb 28 2017
,
Feb 28 2017
> That won't work for our use case where we need to build chrome and libcxx*.a together with LTO. It will, you'll just get less LTO, right? I think it's better to make some progress (modern c++ headers) instead of not making progress on trying to solve all the problems at once.
,
Feb 28 2017
> It will, you'll just get less LTO, right? Not only less LTO, but also less CFI. > I think it's better to make some progress Of course!
,
May 5 2017
,
Jul 17 2017
dup of 593874?
,
Jul 17 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by thakis@chromium.org
, Dec 14 2016