From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 100788 invoked by alias); 7 Nov 2016 19:21:19 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 100743 invoked by uid 89); 7 Nov 2016 19:21:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Message-ID: <1478546473.7146.875.camel@localhost.localdomain> Subject: Re: [PATCH] nptl: Document the reason why __kind in pthread_mutex_t is part of the ABI From: Torvald Riegel To: Florian Weimer Cc: GNU C Library Date: Mon, 07 Nov 2016 19:21:00 -0000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-11/txt/msg00251.txt.bz2 On Mon, 2016-11-07 at 14:47 +0100, Florian Weimer wrote: > I started composing a lengthy email about why we should align > pthread_mutex_t layout on i386 and x86_64 (because cross-process > compatibility is of more practical importance these days than > LinuxThreads backwards compatibility). But then I realized that we > don't have this choice due to the static initializers, which have __kind > at different offsets. > > The attached patch makes this more explicit in the relevant header files. OK.