https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65500
--- Comment #1 from dave.anglin at bell dot net ---
On 2015-03-20, at 5:00 PM, danglin at gcc dot gnu.org wrote:
> FAIL: 17_intro/headers/c++2014/all_attributes.cc (test for excess errors)
> Excess errors:
> /test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/include/shared_mutex:64:34:
> error: narrowing conversion of '35985' from 'int' to 'short int' inside { }
>
> The define in sys/pthread.h is:
> #define __LWP_RWLOCK_VALID 0x8c91
It looks like this bug was triggered by this change:
2015-03-18 Jonathan Wakely <jwak...@redhat.com>
Torvald Riegel <trie...@redhat.com>
* acinclude.m4 (GLIBCXX_CHECK_GTHREADS): Check for pthread_rwlock_t.
* config.h.in: Regenerate.
* configure: Regenerate.
* include/std/shared_mutex: Check _GLIBCXX_USE_PTHREAD_RWLOCK_T.
(shared_timed_mutex::_M_rwlock): Use PTHREAD_RWLOCK_INITIALIZER.
(shared_timed_mutex::lock_shared()): Retry on EAGAIN.
(shared_timed_mutex::try_lock_shared_until()): Retry on EAGAIN and
EDEADLK.
At one time, GCC was permissive about system header issues, particularly when
they aren't
really a problem. Is this still the case?
It looks like an include hack would fix but there's probably more issues like
this.
Dave
--
John David Anglin dave.ang...@bell.net
