From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 110487 invoked by alias); 22 Jan 2018 16:00:34 -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 108652 invoked by uid 89); 22 Jan 2018 16:00:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=states, reserved X-HELO: mx1.redhat.com Subject: Re: glibc 2.27: less than two weeks till release To: Joseph Myers , Szabolcs Nagy Cc: Romain Naour , libc-alpha@sourceware.org, nd@arm.com References: <20180118175601.GC31922@altlinux.org> <757fb450-6532-0a87-d79e-6744bb7321b1@gmail.com> <5A65C6C7.3080005@arm.com> From: Florian Weimer Message-ID: Date: Mon, 22 Jan 2018 16:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2018-01/txt/msg00709.txt.bz2 On 01/22/2018 04:48 PM, Joseph Myers wrote: > On Mon, 22 Jan 2018, Szabolcs Nagy wrote: > >> on aarch64 a list of cpu states (e.g fp registers) can only be >> accessed via parsing the __reserved member (there are no macros >> or functions defined for this, the user has to manually cast). > > If there are semantics beyond simply being reserved, there needs to be a > prominent comment explaining how there are already such semantics in > current kernel etc. versions, since any field that is just reserved should > be named using the __glibc_reserved convention, not __reserved, __unused, > __pad etc. (and __reserved without such an explanation thus looks like a > field that should be renamed to conform to normal glibc coding style). It is reserved space for dynamic allocations, similar to the __space field in struct scratch_buffer, and the context data contains offsets relative to the start of the field. It is in active use today and not intended for future expansion. Thanks, Florian