public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alistair Francis <alistair23@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Allow memset local PLT reference for RISC-V.
Date: Thu, 17 Sep 2020 18:02:33 +0000 (GMT)	[thread overview]
Message-ID: <20200917180233.71416398BC1C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d38e1bbda0be2d184f0496001cfeab00216fe01c

commit d38e1bbda0be2d184f0496001cfeab00216fe01c
Author: Alistair Francis <alistair.francis@wdc.com>
Date:   Fri Jun 19 09:00:23 2020 -0700

    Allow memset local PLT reference for RISC-V.
    
    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.
    
    From the original commit for power-pc:
        Since memset is documented as a function GCC may always implicitly
        generate calls to, it seems reasonable to allow that local PLT
        reference (just like those for libgcc functions that GCC implicitly
        generates calls to and that are also exported from libc.so), which
        this patch does.
    
    Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>

Diff:
---
 sysdeps/unix/sysv/linux/riscv/localplt.data | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sysdeps/unix/sysv/linux/riscv/localplt.data b/sysdeps/unix/sysv/linux/riscv/localplt.data
index 0ed8650b65..0a235592c3 100644
--- a/sysdeps/unix/sysv/linux/riscv/localplt.data
+++ b/sysdeps/unix/sysv/linux/riscv/localplt.data
@@ -5,6 +5,7 @@ libc.so: calloc
 libc.so: free
 libc.so: malloc
 libc.so: memalign
+libc.so: memset ?
 libc.so: realloc
 # The TLS-enabled version of these functions is interposed from libc.so.
 ld.so: _dl_signal_error


                 reply	other threads:[~2020-09-17 18:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200917180233.71416398BC1C@sourceware.org \
    --to=alistair23@sourceware.org \
    --cc=glibc-cvs@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).