From owner-freebsd-current Fri Feb 25 6:10:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 0AD2537BA81 for ; Fri, 25 Feb 2000 06:10:38 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 28583 invoked from network); 25 Feb 2000 14:10:31 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 25 Feb 2000 14:10:31 -0000 Date: Sat, 26 Feb 2000 01:10:26 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Martin Cracauer Cc: David O'Brien , jdp@FreeBSD.ORG, jkh@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: extern variables in shared libraries broken (ld.so or mmap bug) In-Reply-To: <20000225134708.B16847@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Feb 2000, Martin Cracauer wrote: > It is also not clear to me that the new assembler really fixes the > bug. While I cannot judge over the correctness of the syntax, I think > it is possible that the new assembler still works on the same syntax, > not recognizing the parameterless GOTOFF our gcc generates. I happen to have a Linux gas built from a relatively recent version of binutils. It still has the problem. Surprisingly, both assemblers handle: leal foo@GOTOFF,%eax but neither handles the equivalent: movl $foo@GOTOFF,%eax > It is possible that we indroduced the bug by our profiling changes? > The line in i386.c that generates the code in question is from > revision 1.5, which is the profiling delta from the original gcc. In > that case we can't count on a new gas fixing it for us. Reverting to the FSF version of i386.c didn't fix the problem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message