From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joseph Myers Newsgroups: gmane.comp.lib.glibc.alpha,gmane.emacs.devel Subject: Re: Removal of unexec support from glibc malloc Date: Mon, 18 Jan 2016 22:27:25 +0000 Message-ID: References: <569CDB81.6040600@redhat.com> <569D3BE0.6050103@cs.ucla.edu> <569D4157.7050408@dancol.org> <569D432F.9070308@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Trace: ger.gmane.org 1453156081 29508 80.91.229.3 (18 Jan 2016 22:28:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Jan 2016 22:28:01 +0000 (UTC) Cc: Zack Weinberg , , GNU C Library To: Daniel Colascione Original-X-From: libc-alpha-return-66378-glibc-alpha=m.gmane.org@sourceware.org Mon Jan 18 23:27:51 2016 Return-path: Envelope-to: glibc-alpha@plane.gmane.org Original-Received: from server1.sourceware.org ([209.132.180.131] helo=sourceware.org) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aLIH8-0003JQ-EF for glibc-alpha@plane.gmane.org; Mon, 18 Jan 2016 23:27:50 +0100 DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=tqtrD 9kiHlz2/RGJ/7vGKkQRvf70638iimZlF53EytxHn/ZQGJvI65MRdN60QYOpGlDUM HH0S4+CrG7RV81d0xjpERmT+/sVn7kaU0y1AaX8UK90Xl6EEJtkgaXbHMw02Q73u 18kNdiozjfZHzyll3naSP9XxJNugzsNznb+ZPU= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=j9F85ohzbmw 5Hrxw611XC4NEEVg=; b=pud5+eQso9aaj+5hmwO0GK+cvKqfeqG/BD5+548QMNV yStOMurG6phMCDw70xn1QJzlGJ1Yu3kj85/qUi/GuzAbyrdPp+dzLHyamd80KX5R jFE8O8SMd3z/mR172AVwCYpTEJ3J0oucYLAF054pk6U1Axdmpa+Duv4XoD76D49Q = Original-Received: (qmail 13741 invoked by alias); 18 Jan 2016 22:27:44 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Original-Sender: libc-alpha-owner@sourceware.org Original-Received: (qmail 12788 invoked by uid 89); 18 Jan 2016 22:27:43 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=ABIs, abis, cooperate X-HELO: relay1.mentorg.com In-Reply-To: <569D432F.9070308@dancol.org> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) Xref: news.gmane.org gmane.comp.lib.glibc.alpha:58661 gmane.emacs.devel:198308 Archived-At: On Mon, 18 Jan 2016, Daniel Colascione wrote: > On 01/18/2016 11:54 AM, Zack Weinberg wrote: > > On Mon, Jan 18, 2016 at 2:47 PM, Daniel Colascione wrote: > >> > >> As long as the ABI support is there, we can keep using the "separate > >> malloc implementation" even if glibc doesn't cooperate by providing > >> convenient headers to access it. > > > > Clarification: it will not be possible to link new executables against > > the symbols in question. (This is what a "compat symbol" in glibc is - > > available only to existing binaries, not to new invocations of ld.) > > Oh, with a linker script or other hackery, I'm sure I could make it > available to new invocations of ld. It's just bytes. Being a compat symbol also means that future architecture ports and ABIs don't include the functionality at all. -- Joseph S. Myers joseph@codesourcery.com