public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] string: Disable stack protector for memset in early static initialization
Date: Tue, 23 Jan 2024 13:23:53 +0000 (GMT)	[thread overview]
Message-ID: <20240123132353.7A3B63858022@sourceware.org> (raw)

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

commit 77c6a2717de1b6a78e79538b2074579ed77839ed
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Mon Jan 22 10:42:19 2024 -0300

    string: Disable stack protector for memset in early static initialization
    
    For ports that use the default memset, the compiler might generate early
    calls before the stack protector is initialized (for instance, riscv
    with -fstack-protector-all on _dl_aux_init).
    
    Checked on riscv64-linux-gnu-rv64imafdc-lp64d.
    
    Reviewed-by: Florian Weimer <fweimer@redhat.com>

Diff:
---
 string/Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/string/Makefile b/string/Makefile
index 3ba77e1b2f..8f31fa49e6 100644
--- a/string/Makefile
+++ b/string/Makefile
@@ -270,6 +270,7 @@ CFLAGS-memcpy.c += $(no-stack-protector)
 CFLAGS-wordcopy.c += $(no-stack-protector)
 # Called during static initialization
 CFLAGS-strncmp.c += $(no-stack-protector)
+CFLAGS-memset.c += $(no-stack-protector)
 
 CFLAGS-argz-next.c += $(config-cflags-wno-ignored-attributes)
 CFLAGS-basename.c += $(config-cflags-wno-ignored-attributes)

                 reply	other threads:[~2024-01-23 13:23 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=20240123132353.7A3B63858022@sourceware.org \
    --to=azanella@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).