[STDCXX-1066] SPARCV8 requires pthread_mutex_t and pthread_cond_t to be aligned on an 8-byte boundary

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 4.2.1, 4.2.2, 4.2.x, 4.3.x
• Fix Version/s: 4.2.2, 4.2.x, 4.3.x
• Component/s: Thread Safety
• Labels: features runtime threads

Environment

Solaris 10 Update 6 or later on SPARCV8 [32-bit]
Defect is compiler-independent - in reality it only affects Sun Studio and GCC.

• Regression: Unit Test Broken
• Severity: Incorrect Behavior
• Assignee: Unassigned
• Reporter: Stefan Teleman
• Created: 31/Aug/12 19:21
• Updated: 28/Sep/12 22:21
• Resolved: 28/Sep/12 22:21

Description

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.

Issue Links

• is related to: STDCXX-1072 [Oracle Solaris/SPARCV8] stricter mutex alignment requirements