From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Alistair Francis <alistair23@gmail.com>,
"Maciej W. Rozycki" <macro@wdc.com>,
Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Problem with RISC-V
Date: Tue, 8 Sep 2020 09:02:35 -0700 [thread overview]
Message-ID: <CAMe9rOpKm83RBukW3+nNhhAAEuR6vezeWTZRDcDOHSfwHmvqEg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2009081553510.8874@digraph.polyomino.org.uk>
On Tue, Sep 8, 2020 at 8:57 AM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Mon, 7 Sep 2020, Joseph Myers wrote:
>
> > On Mon, 7 Sep 2020, Alistair Francis via Libc-alpha wrote:
> >
> > > Yep, that is probably the PLT failure. The RV32 tests fail with a PLT error.
> > >
> > > It's a problem in binutils and a patch has been sent. The decision was to not
> > > do anything in glibc and just wait for binutils to update.
> >
> > I asked about a binutils backport in
> > <https://sourceware.org/pipermail/libc-alpha/2020-August/117334.html>. I
> > don't believe I saw any response to that, but I still think a backport
> > would be a good idea.
>
> Also, that particular binutils commit doesn't actually seem to fix things
> - there is still
>
> Extra PLT reference: libc.so: memset
Is this related?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67220
--
H.J.
next prev parent reply other threads:[~2020-09-08 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 13:11 Lukasz Majewski
2020-09-07 13:29 ` Adhemerval Zanella
2020-09-07 15:22 ` Alistair Francis
2020-09-07 16:52 ` Joseph Myers
2020-09-08 15:57 ` Joseph Myers
2020-09-08 16:02 ` H.J. Lu [this message]
2020-09-08 16:39 ` Joseph Myers
2020-09-08 19:47 ` Alistair Francis
2020-09-08 20:25 ` Joseph Myers
2020-09-12 21:49 ` Alistair Francis
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=CAMe9rOpKm83RBukW3+nNhhAAEuR6vezeWTZRDcDOHSfwHmvqEg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@wdc.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).