From: John Marino <binutils@marino.st>
To: binutils@sourceware.org
Subject: Re: gold linker 2.22 regressed for DragonFly
Date: Mon, 02 Jan 2012 19:27:00 -0000 [thread overview]
Message-ID: <4F0204FA.2090305@marino.st> (raw)
In-Reply-To: <mcr4nwe2bmv.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
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
next prev parent reply other threads:[~2012-01-02 19:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 22:16 John Marino
2011-12-02 4:59 ` Ian Lance Taylor
2011-12-02 8:44 ` John Marino
2011-12-02 14:28 ` Ian Lance Taylor
2011-12-31 16:40 ` John Marino
2012-01-02 2:05 ` Ian Lance Taylor
2012-01-02 9:36 ` John Marino
2012-01-02 18:38 ` Ian Lance Taylor
2012-01-02 19:27 ` John Marino [this message]
2012-01-02 19:48 ` John Marino
2012-01-02 22:56 ` John Marino
2012-01-03 9:20 ` gold linker 2.22 regressed for DragonFly [revised testsuite results] John Marino
2012-01-05 18:32 ` Ian Lance Taylor
2012-01-06 10:24 ` John Marino
2012-01-06 14:43 ` Ian Lance Taylor
2012-01-06 20:04 ` John Marino
2012-01-22 18:59 ` John Marino
2012-01-22 19:43 ` Ian Lance Taylor
2012-01-22 20:46 ` John Marino
2012-01-23 16:49 ` Ian Lance Taylor
2012-01-03 19:43 ` gold linker 2.22 regressed for DragonFly Ian Lance Taylor
2012-01-05 17:30 ` John Marino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0204FA.2090305@marino.st \
--to=binutils@marino.st \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).