From: John Marino <binutils@marino.st>
To: binutils@sourceware.org
Subject: Re: gold linker 2.22 regressed for DragonFly [revised testsuite results]
Date: Fri, 06 Jan 2012 10:24:00 -0000 [thread overview]
Message-ID: <4F06CBE0.6080109@marino.st> (raw)
In-Reply-To: <mcrd3ayt2zy.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
On 1/5/2012 7:31 PM, Ian Lance Taylor wrote:
>> 2. ver_matching_test.sh: __bss_start not local, rtld issue? real issue? (failed on v2.21 too)
>
> Hard to understand why this would fail. The __bss_start symbol is
> defined automatically by the linker itself.
ok. I thought I remembered seeing references to __bss_start in rtld
code, so I suspected rtld was the culprit.
>> 3. exception_static_test: likely real problem. gdb log attached
>
> My first guess would be that DragonFly does not support dl_iterate_phdr,
> or that it does not work correctly for statically linked executables.
> That's just a guess, though.
I brought in dl_iterate_phdr support to dragonfly (system compiler is
4.4.7 snapshot, 2011-10-25), and it appears to be working although maybe
in the case of statically linked executables it's not. What handles the
latter? Is that an rtld thing?
>> 4. intpri2: likely real problem. gdb log attached
>
> This is almost certainly the same issue as the --no-ctors-in-init-array
> issue: DragonFly does not suppor DT_INIT_ARRAY.
If I wanted to add DT_INIT_ARRAY support to DragonFly, what component
needs to be updated? again rtld?
>> 5. relro_test: no relro support in rtld, ignore
>> 6. relro_now_test: no relro support in rtld, ignore
>> 7. relro_strip_test: no relro support in rtld, ignore
>
> Yeah, if the dynamic linker does not handle relro, then these tests are
> expected to fail.
>
> Ian
As far as I can tell, no BSD supports relro and it seems to be of
limited value so I don't suspect this will change any time soon.
Regards,
John
next prev parent reply other threads:[~2012-01-06 10:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 22:16 gold linker 2.22 regressed for DragonFly 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
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 [this message]
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=4F06CBE0.6080109@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).