From: Alistair Francis <alistair23@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Alistair Francis via Libc-alpha <libc-alpha@sourceware.org>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] Allow memset local PLT reference for RISC-V.
Date: Wed, 24 Jun 2020 15:25:06 -0700 [thread overview]
Message-ID: <CAKmqyKP7oPUacAmgGFS-2kQHRFvaeTt8g0tVTv=yu-QGquwZzg@mail.gmail.com> (raw)
In-Reply-To: <87zh8u8d17.fsf@igel.home>
On Tue, Jun 23, 2020 at 12:19 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> On Jun 22 2020, Alistair Francis via Libc-alpha wrote:
>
> > This is similar to commit a26e2e9feab87d4f745c31411458b048742ac733
> > "Allow memset local PLT reference for powerpc soft-float.".
> >
> > GCC 10.1 results in the localplt test failing for RISC-V.
>
> Why doesn't the redirect in sysdeps/generic/symbol-hacks.h work?
I'm not sure.
I suspect it's the same reason it didn't work in the commit this is
based off: a26e2e9feab87d4f745c31411458b048742ac733
"Allow memset local PLT reference for powerpc soft-float.".
The error is part of glibc's check scripts. I'm assuming memset is in
the binary which produces a check failure as we don't expect it to be.
I'm not sure where sysdeps/generic/symbol-hacks.h is involved in this
process though.
Alistair
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
> "And now for something completely different."
next prev parent reply other threads:[~2020-06-24 22:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 21:10 Alistair Francis
2020-06-23 7:19 ` Andreas Schwab
2020-06-24 22:25 ` Alistair Francis [this message]
2020-06-25 7:20 ` Florian Weimer
2020-06-25 18:16 ` Vineet Gupta
2020-06-25 18:41 ` Florian Weimer
2020-06-26 3:58 ` Vineet Gupta
2020-06-29 9:11 ` Florian Weimer
2020-06-29 15:58 ` Alistair Francis
2020-06-29 16:00 ` Alistair Francis
2020-06-29 16:18 ` Florian Weimer
2020-06-29 16:11 ` Florian Weimer
2020-06-29 16:15 ` Alistair Francis
2020-06-29 16:30 ` Florian Weimer
2020-06-29 16:25 ` Alistair Francis
2020-06-29 16:39 ` Florian Weimer
2020-06-29 16:39 ` Alistair Francis
2020-06-29 16:53 ` Florian Weimer
2020-06-29 17:01 ` Andreas Schwab
2020-06-29 17:05 ` Florian Weimer
2020-06-29 17:44 ` Andreas Schwab
2020-06-30 0:26 ` Jim Wilson
2020-07-01 0:45 ` Maciej W. Rozycki
2020-07-10 21:35 ` Alistair Francis
2020-07-10 22:34 ` H.J. Lu
2020-07-12 1:32 ` Maciej W. Rozycki
2020-07-14 2:07 ` RISC-V: `ld.so' fails linking against `libgcc.a' built at `-O0' (was: Re: [PATCH] Allow memset local PLT reference for RISC-V.) Maciej W. Rozycki
2020-07-14 5:21 ` RISC-V: `ld.so' fails linking against `libgcc.a' built at `-O0' Andreas Schwab
2020-07-14 6:27 ` Richard Biener
2020-07-14 9:35 ` Maciej W. Rozycki
2020-08-20 22:39 ` [PATCH] Allow memset local PLT reference for RISC-V Alistair Francis
2020-08-21 10:44 ` Maciej W. Rozycki
2020-08-27 18:31 ` Alistair Francis
2020-09-12 21:51 ` Alistair Francis
2020-06-29 17:00 ` Andreas Schwab
2020-06-29 17:13 ` Florian Weimer
2020-06-29 17:46 ` Andreas Schwab
2020-06-25 0:20 ` Vineet Gupta
2020-06-25 21:27 ` Palmer Dabbelt
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='CAKmqyKP7oPUacAmgGFS-2kQHRFvaeTt8g0tVTv=yu-QGquwZzg@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).