From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12483 invoked by alias); 20 Apr 2012 23:36:32 -0000 Received: (qmail 12397 invoked by uid 22791); 20 Apr 2012 23:36:30 -0000 X-SWARE-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-qa0-f54.google.com (HELO mail-qa0-f54.google.com) (209.85.216.54) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Apr 2012 23:36:01 +0000 Received: by qao25 with SMTP id 25so674654qao.20 for ; Fri, 20 Apr 2012 16:36:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.75.142 with SMTP id y14mr2596956qcj.144.1334964960606; Fri, 20 Apr 2012 16:36:00 -0700 (PDT) Received: by 10.229.136.69 with HTTP; Fri, 20 Apr 2012 16:36:00 -0700 (PDT) In-Reply-To: References: <20120420165552.q36l2rh45cwwsokw-nzlynne@webmail.spamcop.net> Date: Fri, 20 Apr 2012 23:36:00 -0000 Message-ID: Subject: Re: RFC: Add STB_GNU_SECONDARY From: "H.J. Lu" To: Ian Lance Taylor Cc: Cary Coutant , Joern Rennecke , "Ansari, Zia" , GCC Development , GNU C Library , Binutils Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2012-04/txt/msg00752.txt.bz2 On Fri, Apr 20, 2012 at 3:59 PM, Ian Lance Taylor wrote: > "H.J. Lu" writes: > >> On Fri, Apr 20, 2012 at 3:10 PM, Cary Coutant wrot= e: >>>> We only have very few bits to in STB_XXX field. >>> >>> This is exactly why I'm not in favor of this extension. The feature >>> doesn't seem compelling enough to use up one of these precious >>> reserved values (in fact, you're using the next-to-last one that's >>> reserved for OS use). >>> >>> You want a backup definition? Put a weak def at the end of the link lin= e. >>> >> >> It doesn't work for us since the backup definition is >> always used even if there is a normal definition in >> a shared library or an archive. > > Can you expand on that? =A0How can you refer to the backup definition if > there is a normal definition? > We need a definition for symbol, foo. Since we don't know if there is a definition of foo at the final link time. We provide the backup definition for foo. The backup one is ignored if there is a normal one in an archive or DSO at link time. --=20 H.J.