Hello, This is the first of a batch of changes for VxWorks, fixing issues observed when activating libstdc++ and the associated testing. Many of the issues are just plain bugs not (libstd)c++ specific; they are just more easily exposed in a c++ testing context.
CC'ed Joel and Jerome on this starter one as they have been
involved in this activity very closely. I'll then cc individual
contributors on subsequent patches, in addition to listing them
in the ChangeLog entry headers.
Most changes were initially developed for gcc-8 based
toolchains.
They were first proposed, reorganized and adjusted in-house for
our gcc-9 based tree, then tested for powerpc-vxworks6 and aarch64-vxworks7
where we now have clean results on a few Ada oriented internal
testsuites and much improved results on gcc/g++/libstdc++ testsuites,
for a mix of RTP and kernel mode runs.
I then verified on mainline that I could build a powerpc-vxworks6
toolchain and that a couple of internal testuites pass with this
compiler as well.
--
This change guards the #inclusion of vxAtomicLib.h from
gthr-vxworks.h so it only takes place in the LIBGC2 context
where we need it.
This fixes build failures of libstdc++ when activated,
caused by uses of gthr-vxworks.h in c++98 compilation contexts
while vxAtomicLib.h for C++ requires C++ >= 11.
Olivier
2019-12-12 Olivier Hainque <hain...@adacore.com>
libgcc/
* config/gthr-vxworks.h: Guard #include vxAtomicLib.h
by IN_LIBGCC2.
0002-Guard-inclusion-of-vxAtomicLib.h-from-gthr-vxworks.h.patch
Description: Binary data
