From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 107898 invoked by alias); 25 Jun 2018 20:33:17 -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 107868 invoked by uid 89); 25 Jun 2018 20:33:16 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=EI_ABIVERSION, ei_abiversion, Hx-languages-length:765 X-HELO: albireo.enyo.de From: Florian Weimer To: "Maciej W. Rozycki" Cc: , Alan Modra Subject: Re: [PATCH 2/2] libc-abis: Define ABSOLUTE ABI [BZ #19818][BZ #23307] References: Date: Mon, 25 Jun 2018 20:33:00 -0000 In-Reply-To: (Maciej W. Rozycki's message of "Mon, 18 Jun 2018 19:07:50 +0100") Message-ID: <87sh5a38tz.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2018-06/txt/msg00759.txt.bz2 * Maciej W. Rozycki: > Define a new ABSOLUTE ABI for static linker's use with EI_ABIVERSION > where correct absolute (SHN_ABS) symbol run-time load semantics is > required. This way it can be ensured at static link time that a program > or DSO will not suffer from previous semantics where absolute symbols > were relocated by the base address, or symbols whose `st_value' is zero > silently ignored leading to a confusing "undefined symbol" error message > at load time, and instead "ELF file ABI version invalid" is printed with > old dynamic loaders, making it clear that there is an ABI version > incompatibility. Is this really necessary? It essentially precludes backporting the fixes.