From: John Marino <binutils@marino.st>
To: Ian Lance Taylor <iant@google.com>
Cc: binutils@sourceware.org
Subject: Re: gold linker 2.22 regressed for DragonFly
Date: Sat, 31 Dec 2011 16:40:00 -0000 [thread overview]
Message-ID: <4EFF3AF3.3080404@marino.st> (raw)
In-Reply-To: <mcrpqg7hwux.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
On 12/2/2011 3:27 PM, Ian Lance Taylor wrote:
> John Marino <binutils@marino.st> writes:
>
>> I need to stress that gold built with ld does not have this problem.
>> It's only gold built with gold that segfaults. Does that affect your
>> answer?
>
> Try using the gold option --no-ctors-in-init-array.
>
> Ian
I'm sorry that I had to put this away for a while, but I've picked it
back up today.
Gold build with ld will function without segfaults and produces executables.
Gold build with gold segfaults. It ignores all command-line options.
I modified the makefile to set optimization level to 0. That let me see
the values of variables in gdb. Using gdb on ld-new (gold built with
ld), "print options" on gdb shows a properly defined option set of
General_options class. Doing the same for ld1 (gold built by gold)
shows every single option with null pointers. Not even strings like
"Report usage information" and "Report version information" are included.
So the problem lies in options.h within the General_options class. I
have no idea what ld-new is doing wrong such that ld1 can't built its
option set. These definitions are built with macros though.
John
next prev parent reply other threads:[~2011-12-31 16:40 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 [this message]
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
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=4EFF3AF3.3080404@marino.st \
--to=binutils@marino.st \
--cc=binutils@sourceware.org \
--cc=iant@google.com \
/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).