From: "Carlos O'Donell" <carlos@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>,
Kyle McMartin <kmcmarti@redhat.com>
Subject: Re: [PATCH] arm: Fix R_ARM_IRELATIVE for REL relocs.
Date: Thu, 29 Aug 2013 04:17:00 -0000 [thread overview]
Message-ID: <521ECB3A.4040209@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1308281609120.752@digraph.polyomino.org.uk>
On 08/28/2013 12:14 PM, Joseph S. Myers wrote:
> On Wed, 28 Aug 2013, Carlos O'Donell wrote:
>
>> 2013-08-28 Kyle McMartin <kmcmarti@redhat.com>
>> Carlos O'Donell <carlos@redhat.com>
>>
>> * sysdeps/arm/dl-machine [!RTLD_BOOTSTRAP] (elf_machine_rel):
>> Pass GLRO(dl_hwcap) to the IFUNC resolver.
>
> OK, given a bug filed in Bugzilla and a corresponding [BZ #N] notation and
> entry in NEWS for the fixed bug.
I created BZ# 15905.
Sorry for forgetting, and thanks for reminding me.
I've checked in the patch which fixes the failures we're
seeing in Fedora on this hardware.
> Have you verified that all ARM instances
> of such code now consistently pass the HWCAP value?
Yes.
There are 4 places that require dl_hwcap to be used:
* ifunc-impl-list.c (__libc_ifunc_impl_list) - Already uses dl_hwcap.
* dl-irel.h (elf_ifunc_invoke) - Already uses dl_hwcap. Was fixed by
Richard Henderson in commit 73da6bacf (along with other instances
in dl-machine.h).
* dl-machine.h (elf_machine_rel) - Fixed by this patch.
* dl-machine.h (elf_machine_rela) - Fixed by Will Newton's patch.
These are the only place that I know about that require using
dl_hwcap and all of them are now fixed.
The uses are inconsistent in their use of `unsigned long int'
vs. 'int' for the dl_hwcap parameter, but changing that could
be a future cleanup.
I will note that the 32-bit ARM testsuite on this hardware is
not clean e.g.
make[2]: *** [/home/codonell/build/math/test-fenv.out] Error 1
make[1]: *** [math/tests] Error 2
make[2]: *** [/home/codonell/build/stdio-common/bug22.out] Error 1
make[1]: *** [stdio-common/tests] Error 2
make[2]: [/home/codonell/build/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/home/codonell/build/nptl/tst-cleanup2.out] Error 1
make[2]: *** [/home/codonell/build/nptl/tst-cleanupx2.out] Error 1
make[1]: *** [nptl/tests] Error 2
make[2]: [/home/codonell/build/conform/run-conformtest.out] Error 1 (ignored)
make[2]: *** [/home/codonell/build/elf/ifuncmain5picstatic.out] Error 139
make[1]: *** [elf/tests] Error 2
make[1]: *** [/home/codonell/build/check-local-headers.out] Error 1
make: *** [check] Error 2
In particular ifuncmain5picstatic.out looks troublesome, and
I need to look at it to see if something is further wrong with
the IFUNC support.
Cheers,
Carlos.
next prev parent reply other threads:[~2013-08-29 4:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 4:23 Carlos O'Donell
2013-08-28 16:14 ` Joseph S. Myers
2013-08-29 4:17 ` Carlos O'Donell [this message]
2013-08-29 10:00 ` Will Newton
2013-08-29 12:25 ` Joseph S. Myers
2013-08-29 19:18 ` Will Newton
2013-08-29 12:24 ` Joseph S. Myers
2013-08-29 19:27 ` Joseph S. Myers
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=521ECB3A.4040209@redhat.com \
--to=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=kmcmarti@redhat.com \
--cc=libc-ports@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).