https://bugs.kde.org/show_bug.cgi?id=358478
Bug ID: 358478
Summary: drd/tests/std_thread.cpp doesn't build with GCC6
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: drd
Assignee: [email protected]
Reporter: [email protected]
g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -I../../coregrind
-I../../include -I../../VEX/pub -I../../VEX/pub -DVGA_amd64=1 -DVGO_linux=1
-DVGP_amd64_linux=1 -DVGPV_amd64_linux_vanilla=1 -DVGA_SEC_x86=1
-DVGP_SEC_amd64_linux=1 -Winline -Wall -Wshadow -Wno-long-long -g
-fno-stack-protector -m64 -Wextra -Wno-inline -Wno-unused-parameter -std=c++0x
-MT std_thread-std_thread.o -MD -MP -MF .deps/std_thread-std_thread.Tpo -c -o
std_thread-std_thread.o `test -f 'std_thread.cpp' || echo './'`std_thread.cpp
std_thread.cpp: In function ‘void* execute_native_thread_routine(void*)’:
std_thread.cpp:30:3: error: ‘_Impl_base’ is not a member of ‘std::thread’
std::thread::_Impl_base* __t = static_cast<std::thread::_Impl_base*>(__p);
^~~
This is with gcc (GCC) 6.0.0 20160123 (experimental) and happens because the
testcase tries to build with some copied/internal thread representation details
"From libstdc++-v3/src/c++11/thread.cc". But those implementation details don't
match anymore. Unfortunately I don't fully understand what is being tested to
be able to fix this.
Note that in general valgrind currently doesn't build with GCC6 because of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69454 which seems to be triggered
by our use of -mpreferred-stack-boundary=2
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.