From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21470 invoked by alias); 11 Feb 2002 19:54:41 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 21238 invoked from network); 11 Feb 2002 19:54:37 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 11 Feb 2002 19:54:37 -0000 Received: from porcupine.cygnus.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id LAA00021 for ; Mon, 11 Feb 2002 11:54:34 -0800 (PST) Received: from porcupine.cygnus.com (law@localhost) by porcupine.cygnus.com (8.11.6/8.11.6) with ESMTP id g1BJvfW02142; Mon, 11 Feb 2002 12:57:41 -0700 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 To: "John David Anglin" cc: binutils@sources.redhat.com Subject: Re: Special names tha ld needs to recognize for hppa64-hp-hpux11.X Reply-To: law@redhat.com From: law@redhat.com In-reply-to: Your message of Mon, 11 Feb 2002 12:08:10 EST. <200202111708.g1BH8AIA009479@hiauly1.hia.nrc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Feb 2002 13:48:00 -0000 Message-ID: <2141.1013457460@porcupine.cygnus.com> X-SW-Source: 2002-02/txt/msg00378.txt.bz2 In message <200202111708.g1BH8AIA009479@hiauly1.hia.nrc.ca>, "John David Anglin " writes: > I have a patch that leaves the dynamic-loader defined symbols undefined. > Something additional would be needed if we actually generated a static > binary and need to provide these symbols. Right. This could possibly be an issue for the PA64 Linux folks, but I don't see it being an issue in HP-UX land. > I think so. The ones that are provided are supposed to be linker defined > according to the "PA-64 Runtime Supplement". The only questionable one > is __TLS_SIZE. The HP compiler provides a default value for it equal to > 0xc8 (at least, it does in a trivial program) while the linker script > provides a value of 0. On the other hand, I presume crt0.o initializes > tp (cr27). How does it find the start of .tbss? From the elf header? I suspect __TLS_SIZE can probably be derived by the linker from the size of the various .t* sections. I haven't really studied the HP thread local storage scheme, but I suspect it doesn't need to find the start of tbss, only tdata as the TLS sections should be used just for initializing thread local data. I would expect cr27 to be initialized by crt0 or the kernel. > That's what the HP linker does. However, I am not sure it hurts to define > the dynamic loader symbols in the linker. It's definitely simpler. It could hurt if the symbol is defined by a module that is dl_loaded at runtime. > At the moment, a more serious issue is the treatment of LTOFF_* relocations > in static programs (see my mail on this yesterday). We need to fix this > before a decision can be made on the synamic loader defined symbols. I missed that completely (I've been on the road most of the last week). Can you resend it to me privately? jeff