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] sh: Fix static build with --enable-fortify
Date: Mon, 22 Jan 2024 13:28:36 +0000 (GMT)	[thread overview]
Message-ID: <20240122132836.3F9073858293@sourceware.org> (raw)

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

commit bcf2abd43bbe6ffdd8b6a1e1e36cc67a9769e508
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Tue Jan 16 13:07:47 2024 -0300

    sh: Fix static build with --enable-fortify
    
    For static the internal symbols should not be prepended with the
    internal __GI_.
    
    Checked with a make check for sh4-linux-gnu.

Diff:
---
 sysdeps/unix/sysv/linux/sh/____longjmp_chk.S | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sysdeps/unix/sysv/linux/sh/____longjmp_chk.S b/sysdeps/unix/sysv/linux/sh/____longjmp_chk.S
index ede6551bcc..f61db0bc63 100644
--- a/sysdeps/unix/sysv/linux/sh/____longjmp_chk.S
+++ b/sysdeps/unix/sysv/linux/sh/____longjmp_chk.S
@@ -53,7 +53,7 @@ longjmp_msg:
 .Lstr:							\
 	.long	longjmp_msg@GOTOFF;			\
 .Lfail:							\
-	.long	__GI___fortify_fail@PLT-(.Lfail0-.);	\
+	.long	HIDDEN_JUMPTARGET(__fortify_fail)@PLT-(.Lfail0-.); \
 	cfi_restore_state;
 #else
 # define CALL_FAIL \
@@ -70,7 +70,7 @@ longjmp_msg:
 .Lstr:							\
 	.long	longjmp_msg;				\
 .Lfail:							\
-	.long	__fortify_fail;				\
+	.long	HIDDEN_JUMPTARGET(__fortify_fail);	\
 	cfi_restore_state;
 #endif

                 reply	other threads:[~2024-01-22 13:28 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=20240122132836.3F9073858293@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).