libstdc++: Fix condition for gthreads-timed effective-target
authorJonathan Wakely <jwakely@redhat.com>
Thu, 17 Dec 2020 14:28:17 +0000 (14:28 +0000)
committerJonathan Wakely <jwakely@redhat.com>
Thu, 17 Dec 2020 16:16:37 +0000 (16:16 +0000)
commitb2bc1bb6cabf30f332938d648fe6432a3a9d27b6
tree85cfb18e6fd3d0a0b741aa9d41491ef57309f4e4
parentec2a58a36ae14be4793c04c0bab183734aeb0312
libstdc++: Fix condition for gthreads-timed effective-target

The refactoring in r11-5500 altered the condition for the gthreads-timed
test from #if to #ifdef. For some reason that macro is always defined,
rather than being defined to 1 or undefined like most of our autoconf
macros. That means the test always passes now, even for targets where
the macro is defined to 0 (specifically, Darwin). That causes some tests
to FAIL when they should have been UNSUPPORTED.

This restores the previous behaviour.

libstdc++-v3/ChangeLog:

* testsuite/lib/libstdc++.exp (check_v3_target_gthreads_timed):
Fix condition for _GTHREAD_USE_MUTEX_TIMEDLOCK test.
libstdc++-v3/testsuite/lib/libstdc++.exp