This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] Using protected for math symbols

From: Florian Weimer <fweimer at redhat dot com>
To: Wilco Dijkstra <Wilco dot Dijkstra at arm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
Cc: nd <nd at arm dot com>
Date: Fri, 29 Sep 2017 21:34:18 +0200
Subject: Re: [RFC] Using protected for math symbols
Authentication-results: sourceware.org; auth=none
Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer at redhat dot com
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 52B147E434
References: <DB6PR0801MB2053F4FB2315A96BA5D7E32F837E0@DB6PR0801MB2053.eurprd08.prod.outlook.com>

On 09/29/2017 06:46 PM, Wilco Dijkstra wrote:

An alternative approach to this is to completely remove the __sqrt
variants and use protected symbol visibility. This means math functions
are defined using their real name, internal calls use the real name and
don't generate PLT calls, and no more weak/redirect magic is needed.

I don't think this allows us to address namespace issues with staticlinking.


Thanks,
Florian

References:
- [RFC] Using protected for math symbols
  - From: Wilco Dijkstra

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]