Return-Path: X-Original-To: apmail-stdcxx-dev-archive@www.apache.org Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76581DD9B for ; Sun, 23 Sep 2012 21:24:18 +0000 (UTC) Received: (qmail 18546 invoked by uid 500); 23 Sep 2012 21:24:18 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 18510 invoked by uid 500); 23 Sep 2012 21:24:18 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 18501 invoked by uid 99); 23 Sep 2012 21:24:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Sep 2012 21:24:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of stefan.teleman@gmail.com designates 209.85.212.54 as permitted sender) Received: from [209.85.212.54] (HELO mail-vb0-f54.google.com) (209.85.212.54) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Sep 2012 21:24:13 +0000 Received: by vbmv11 with SMTP id v11so5598749vbm.41 for ; Sun, 23 Sep 2012 14:23:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=akUqt2wPWJlILu2RX3IYcMIe4Gpm50l9COjIj3/p6yw=; b=kh+Bks8j+/+JlGxvPQtbYKE7C1J8C6rtYap3VVTPHXh/n3nlFZcMoJTcAbk9736g/C tFLDB+MbsFwupsotHSyfDYf1OSMqNdLFCyPMUgdkBCMfvmf6jRyIwTOs/Ubx10NqXviv cTiLSMOQUcvjTL0ziEN4I/rTHcKRmKXkVTCXhySg2wKIJ7l6BUAUO2I973x8c2BxVxt0 0zqy4+nCQgVHG+Q+32hRWk9RAneKUcXtY0WSDmi43I/Jj7fuVsogRO/JBp+/6AeiWbwz xb5+3OSuk95zFbo49Lgm+P72SPxusKZV9/+l8gmNGz868TZpPKKs+dVIl9BrGd433OSa T1QQ== MIME-Version: 1.0 Received: by 10.52.99.164 with SMTP id er4mr5186153vdb.128.1348435432027; Sun, 23 Sep 2012 14:23:52 -0700 (PDT) Received: by 10.58.29.164 with HTTP; Sun, 23 Sep 2012 14:23:52 -0700 (PDT) In-Reply-To: <505F7802.7010405@hates.ms> References: <5054B4B1.8040502@hates.ms> <5054EBD1.2010802@hates.ms> <5054F77C.9030406@hates.ms> <505F1E4F.1030300@hates.ms> <505F7802.7010405@hates.ms> Date: Sun, 23 Sep 2012 17:23:52 -0400 Message-ID: Subject: Re: STDCXX-1066 [was: Re: STDCXX forks] From: Stefan Teleman To: dev@stdcxx.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Sun, Sep 23, 2012 at 4:58 PM, Liviu Nicoara wrote: > Stefan, I stumbled upon this: http://tinyurl.com/ceet6ec and this: > http://tinyurl.com/c4h9mgl The first URL is Fujitsu. It doesn't mention anything about the side-effects of KU-137111. It's just a description on how to apply kernel patches. The second URL says this: Due to a change in the implementation of the userland mutexes introduced by CR 6296770 in KU 137111-01, objects of type mutex_t and pthread_mutex_t must start at 8-byte aligned addresses. If this requirement is not satisfied, all non-compliant applications on Solaris/SPARC may fail with the signal SEGV with a callstack similar to the following one or with similar callstacks containing the function mutex_trylock_process. \*_atomic_cas_64(0x141f2c, 0x0, 0xff000000, 0x1651, 0xff000000, 0x466d90) set_lock_byte64(0x0, 0x1651, 0xff000000, 0x0, 0xfec82a00, 0x0) fast_process_lock(0x141f24, 0x0, 0x1, 0x1, 0x0, 0xfeae5780) I think that's pretty clear. What I can share with you is: 1. The SPARC alignment patches as I have submitted them here are present in the official production stdcxx packages released with Solaris 10 and Solaris 11. 2. These patches did not make into the Solaris source code tree and a Solaris product without extensive internal code review. Not to mention testing. --Stefan -- Stefan Teleman KDE e.V. stefan.teleman@gmail.com