diff options
author | Nico Weber <nicolasweber@gmx.de> | 2015-01-27 19:27:39 +0000 |
---|---|---|
committer | Nico Weber <nicolasweber@gmx.de> | 2015-01-27 19:27:39 +0000 |
commit | b1e72eca0caf9bb10d66577573d4845557e61c25 (patch) | |
tree | d304e42bb3d3f77e19110ce2ed10a6fcb04153ec /llvm/unittests/ExecutionEngine/MCJIT/MCJITMultipleModuleTest.cpp | |
parent | e024539ea0ff3db0c11827e3a0585ea46910ecbc (diff) | |
download | bcm5719-llvm-b1e72eca0caf9bb10d66577573d4845557e61c25.tar.gz bcm5719-llvm-b1e72eca0caf9bb10d66577573d4845557e61c25.zip |
[libcxx] Make __wrap_iter work with gcc.
he following snippet doesn't build when using gcc and libc++:
#include <string>
void f(const std::string& s) { s.begin(); }
#include <vector>
void AppendTo(const std::vector<char>& v) { v.begin(); }
The problem is that __wrap_iter has a private constructor. It lists vector<>
and basic_string<> as friends, but gcc seems to ignore this for vector<> for
some reason. Declaring vector before the friend declaration in __wrap_iter is
enough to work around this problem, so do that. With this patch, I'm able to
build chromium/android with libc++. Without it, two translation units fail to
build. (iosfwd already provides a forward declaration of basic_string.)
As far as I can tell, this is due to a gcc bug, which I filed as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64816.
Fixes PR22355.
http://reviews.llvm.org/D7201
llvm-svn: 227226
Diffstat (limited to 'llvm/unittests/ExecutionEngine/MCJIT/MCJITMultipleModuleTest.cpp')
0 files changed, 0 insertions, 0 deletions