From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74664 invoked by alias); 24 Feb 2016 15:30:22 -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 74642 invoked by uid 89); 24 Feb 2016 15:30:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.99 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=highly X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mx2.suse.de X-Virus-Scanned: by amavisd-new at test-mx.suse.de Date: Fri, 01 Jan 2016 00:00:00 -0000 From: Michael Matz To: "H.J. Lu" cc: Carlos O'Donell , Alan Modra , gnu-gabi@sourceware.org Subject: Re: Specify how undefined weak symbol should be resolved in executable In-Reply-To: Message-ID: References: <20160223044029.GE10657@bubble.grove.modra.org> <20160224010458.GF10657@bubble.grove.modra.org> <20160224015659.GH10657@bubble.grove.modra.org> <56CD0FC8.4030202@redhat.com> User-Agent: Alpine 2.20 (LSU 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-SW-Source: 2016-q1/txt/msg00032.txt.bz2 Hi, On Wed, 24 Feb 2016, H.J. Lu wrote: > > Agreed. Anything that brings back weak symbols into the dynamic loader > > is going to be highly suspect to me, and require a lot of explaining. > > I was saying as far as ld was concerned, weak defined and non-weak > defined dynamic symbols would be treated equally at run-time. Do you > agree with me? I at least don't. The difference is that a defined weak symbol (at link edit time) might become undefined at runtime. A defined non-weak symbol can't. So they have to be handled differently. Ciao, Michael.