[ https://issues.apache.org/jira/browse/STDCXX-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Teleman closed STDCXX-1066. ---------------------------------- Resolution: Won't Fix Bug will not be fixed upstream. It is fixed in the Solaris releases. > SPARCV8 requires pthread_mutex_t and pthread_cond_t to be aligned on an > 8-byte boundary > --------------------------------------------------------------------------------------- > > Key: STDCXX-1066 > URL: https://issues.apache.org/jira/browse/STDCXX-1066 > Project: C++ Standard Library > Issue Type: Bug > Components: Thread Safety > Affects Versions: 4.2.1, 4.2.2, 4.2.x, 4.3.x > Environment: Solaris 10 Update 6 or later on SPARCV8 [32-bit] > Defect is compiler-independent - in reality it only affects Sun Studio and > GCC. > Reporter: Stefan Teleman > Labels: features, runtime, threads > Fix For: 4.2.2, 4.2.x, 4.3.x > > Attachments: _config-gcc.h.stdcxx-1066.patch, > _config-sunpro.h.stdcxx-1066.patch, ctype.cpp.stdcxx-1066.patch, > exception.cpp.stdcxx-1066.patch, ios.cpp.stdcxx-1066.patch, > iostream.cpp.stdcxx-1066.patch, iostream.stdcxx-1066.patch, > locale_body.cpp.stdcxx-1066.patch, locale_classic.cpp.stdcxx-1066.patch, > messages.cpp.stdcxx-1066.patch, _mutex.h.stdcxx-1066.patch, > time_put.cpp.stdcxx-1066.patch, use_facet.h.stdcxx-1066.patch > > > Starting with Solaris 10 Update 6, on SPARCV8, pthread_mutex_t and > pthread_cond_t MUST be aligned on an 8-byte boundary. Misaligned access will > result in either SEGV or SIGBUS. > There are numerous places in the multi-threaded version of stdcxx where > pthread_mutex_t and/or pthread_cond_t types are contained within an union, > but with an enforced alignment different than 8. All these instances must be > corrected, and #ifdef-guarded for SPARCV8. > Patches to follow shortly, this is just opening the issue. > Warning: the patchset resolving this issue is very large, and it affects a > large number of files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira