From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 109399 invoked by alias); 16 Mar 2017 08:40:39 -0000 Mailing-List: contact gnu-gabi-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: gnu-gabi-owner@sourceware.org Received: (qmail 109386 invoked by uid 89); 16 Mar 2017 08:40:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.99.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 spammy= X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mx1.redhat.com DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 3CAB580F96 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=pass smtp.mailfrom=fweimer@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 3CAB580F96 Subject: Re: RFC: ABI support for special memory area To: "H.J. Lu" , Suprateeka R Hegde References: <88608944-14c9-9d28-80d1-32283521683b@gmail.com> Cc: Carlos O'Donell , gnu-gabi@sourceware.org From: Florian Weimer Message-ID: <13b95ec6-45be-b02f-bb63-bc1835ecf396@redhat.com> Date: Sun, 01 Jan 2017 00:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Thu, 16 Mar 2017 08:40:38 +0000 (UTC) X-SW-Source: 2017-q1/txt/msg00017.txt.bz2 On 03/15/2017 11:03 PM, H.J. Lu wrote: > After all shared objects and the executable file are loaded, relocations > are processed, for each GNU_MBIND segment in a shared object or the > executable file, run-time loader calls __gnu_mbind_setup with type, > address and length. The default implementation of __gnu_mbind_setup is Is there a specified invocation order for the segments? Does the call happen immediately after relocations for an object are processed, or only after relocations for all objections are processed? If the latter, why can't you use the existing ELF constructor mechanism for this? As far as I understand it, the call to __gnu_mbind_setup would just happen before the constructor calls. Thanks, Florian