public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/nsz/bug27072] Make libc symbols hidden in static PIE
Date: Mon, 11 Jan 2021 10:48:41 +0000 (GMT)	[thread overview]
Message-ID: <20210111104841.0441E38438BA@sourceware.org> (raw)

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

commit 45aaf8c6154298d3e00e8f6e1eb0558875a84121
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Wed Jan 6 11:31:04 2021 +0000

    Make libc symbols hidden in static PIE
    
    Hidden matters with static PIE: extern symbol access in position
    independent code usually involves GOT indirections which needs
    RELATIVE relocs in a static linked PIE. Using So hidden avoids
    indirections and RELATIVE relocs on targets that can access symbols
    pc-relative.
    
    The check should use IS_IN_LIB instead of IS_IN(libc) since all
    static libraries can use hidden visibility to avoid indirections,
    however the test system links objects from libcrypt.a into dynamic
    linked test binaries so hidden does not work there.  I think mixing
    static and shared libc components in the same binary should not be
    supported usage, but to be safe only use hidden in libc.a.
    
    From -static-pie linked 'int main(){}' this shaves off 73 relative
    relocs on aarch64 and reduces code size too.

Diff:
---
 include/libc-symbols.h | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/include/libc-symbols.h b/include/libc-symbols.h
index ea126ae70c..93e63ee889 100644
--- a/include/libc-symbols.h
+++ b/include/libc-symbols.h
@@ -434,13 +434,17 @@ for linking")
   strong_alias(real, name)
 #endif
 
-#if defined SHARED || defined LIBC_NONSHARED \
-  || (BUILD_PIE_DEFAULT && IS_IN (libc))
+#if defined SHARED || defined LIBC_NONSHARED
 # define attribute_hidden __attribute__ ((visibility ("hidden")))
 #else
 # define attribute_hidden
 #endif
 
+/* Mark all symbols hidden in static PIE libc to avoid GOT indirections.  */
+#if BUILD_PIE_DEFAULT && IS_IN (libc) && !defined LIBC_NONSHARED
+# pragma GCC visibility push(hidden)
+#endif
+
 #define attribute_tls_model_ie __attribute__ ((tls_model ("initial-exec")))
 
 #define attribute_relro __attribute__ ((section (".data.rel.ro")))


             reply	other threads:[~2021-01-11 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 10:48 Szabolcs Nagy [this message]
2021-01-12 17:18 Szabolcs Nagy
2021-01-14 11:12 Szabolcs Nagy
2021-01-18 16:16 Szabolcs Nagy
2021-01-19 15:59 Szabolcs Nagy
2021-01-20 15:23 Szabolcs Nagy

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=20210111104841.0441E38438BA@sourceware.org \
    --to=nsz@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).