From: Will Newton <will.newton@linaro.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
"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 10:00:00 -0000 [thread overview]
Message-ID: <CANu=Dmh0LVt+kDbDSLH8thv0G8h3aCaZL=qnBGUHJv74knxfjw@mail.gmail.com> (raw)
In-Reply-To: <521ECB3A.4040209@redhat.com>
On 29 August 2013 05:16, Carlos O'Donell <carlos@redhat.com> wrote:
> 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
This always seems to have failed, not sure if anyone is actively
looking at fixing it.
> 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)
I don't see these failures on Ubuntu raring, but I do see some others
that you haven't listed here:
make[2]: *** [/home/linaro/glibc-build/nptl/tst-align2.out] Error 1
make[2]: *** [/home/linaro/glibc-build/nptl/tst-getpid1.out] Error 1
make[2]: *** [/home/linaro/glibc-build/nptl/tst-getpid2.out] Error 1
I haven't had time to investigate these unfortunately.
> 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.
It's a binutils bug that is fixed in binutils trunk and the 2.23
branch, but not yet in any releases.
https://sourceware.org/git/?p=binutils.git;a=commitdiff;h=f8d29fea418654937fc6f22d817a4eb97159528d
--
Will Newton
Toolchain Working Group, Linaro
next prev parent reply other threads:[~2013-08-29 10:00 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
2013-08-29 10:00 ` Will Newton [this message]
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='CANu=Dmh0LVt+kDbDSLH8thv0G8h3aCaZL=qnBGUHJv74knxfjw@mail.gmail.com' \
--to=will.newton@linaro.org \
--cc=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).