Boost C++ Libraries: Ticket #1810: HP-UX, PA-RISC, GCC 4.1+ sp_counted_base.hpp

component changed; owner set

Marshall Clow — Mon, 14 Apr 2008 15:46:40 GMT

owner set to Peter Dimov
component None → smart_ptr

status changed; cc set

Peter Dimov — Mon, 14 Apr 2008 16:01:16 GMT

cc Boris.Gubenko@… added
status new → assigned

A workaround is to build with BOOST_SP_USE_PTHREADS defined.

I believe that the proper symbol to test is hppa, because hpux is set on HP-UX/IA-64 as well. Our regression tests at the moment only have g++ 3.4.6 for PA-RISC, which is why we missed this problem.

Are you in a position to test the current SVN trunk? If so, I'd appreciate it if you confirm or deny that building with BOOST_SP_USE_SPINLOCK works, so that I can route hppa to use it by default (as is done for ARM due to a similar problem with the sync intrinsics.)

Boris Gubenko — Mon, 14 Apr 2008 16:38:41 GMT

Are you in a position to test the current SVN trunk? If so, I'd appreciate it if you confirm or deny that building with BOOST_SP_USE_SPINLOCK works, so that I can route hppa to use it by default (as is done for ARM due to a similar problem with the sync intrinsics.)

I'll test the current SVN trunk, as requested, and report back here. This platform needs some configuration work (for example, I don't think that wide character support is configured properly), but I could never get to it.

Thanks,

Boris

Boris Gubenko — Tue, 15 Apr 2008 18:01:34 GMT

I ran smart_ptr library tests on PA-RISC with BOOST_SP_USE_PTHREADS defined and everything was fine. This is the same machine I'm using for the SVN trunk tests. The version of gcc is 3.4.2. Unfortunately, I don't have PA-RISC machine with more recent gcc installed.

I believe that the proper symbol to test is hppa, because hpux is set on HP-UX/IA-64 as well

This is correct: hppa is set on PA-RISC only while hpux is set on both PA-RISC and HP-UX/ia64.

Thanks,

Boris

status changed; resolution set

Peter Dimov — Mon, 21 Apr 2008 21:48:03 GMT

status assigned → closed
resolution → fixed

This should be fixed in [44440] (release branch) and [44441] (trunk).

Yves Pausch — Thu, 24 Apr 2008 09:31:30 GMT

Thank you!