From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17680 invoked by alias); 2 Jan 2012 19:27:09 -0000 Received: (qmail 17671 invoked by uid 22791); 2 Jan 2012 19:27:08 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.synsport.com (HELO shepard.synsport.net) (208.69.230.148) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Jan 2012 19:26:54 +0000 Received: from [192.168.1.35] (242.red-81-33-239.dynamicip.rima-tde.net [81.33.239.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id A7A3B435D7 for ; Mon, 2 Jan 2012 13:26:53 -0600 (CST) Message-ID: <4F0204FA.2090305@marino.st> Date: Mon, 02 Jan 2012 19:27:00 -0000 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: binutils@sourceware.org Subject: Re: gold linker 2.22 regressed for DragonFly References: <4ED7FCA6.8090706@marino.st> <4ED88FA5.8050408@marino.st> <4EFF3AF3.3080404@marino.st> <4F017A8B.1000905@marino.st> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00022.txt.bz2 On 1/2/2012 7:38 PM, Ian Lance Taylor wrote: > > What linker are you using to build ld1? > I'm just running a makefile target ">gmake check-TESTS". The makefile makes a copy of ld-new (which is gold) and names the copy ld, so gold is used to build ld1. > You said earlier that gold built with ld does not have a problem. To be clear, I'm trying to convey that the first gold built by the old ld linker doesn't segfault when executed. I don't know how well it works outside of that. > Only gold built with gold segfaults. I am suggesting that you use > --no-ctors-in-init-array when running gold. In fact you should try just > editing options.h to make --no-ctors-in-init-array the default to see if > that fixes all your problems. Editing ld1_LDFLAGS to add --no-ctors-in-init-array is effectively this. Also the title of this post is "gold linker 2.22 REGRESSED for DragonFly". gold linker 2.21 doesn't need this switch to build itself. I edited options.h to set ctors-in-init-array to false, followed by ">gmake clean" and ">gmake check-TESTS". The result is better: ================== All 2 tests passed ================== Then I tried ">gmake check" It got pretty far in the testsuite, complete through "split_i386.sh" and starting failing at incremental-dump.cc due to numerous missing headers. I'm got a separate build directory, so the test might not be accounting for that (e.g. source is in {top}/binutils-2.22 and my build directory is {top}/build-b222). Is that options.h generated or is ctors-in-init-array hardcoded to true? Thanks for your help, John