public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Stafford Horne <shorne@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] or1k: Define PI_STATIC_AND_HIDDEN
Date: Wed,  2 Feb 2022 11:05:37 +0000 (GMT)	[thread overview]
Message-ID: <20220202110537.038853858D1E@sourceware.org> (raw)

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

commit 3f35e7d193b7ff098467996ebf85b19c41d6d86e
Author: Stafford Horne <shorne@gmail.com>
Date:   Sat Jan 29 08:20:40 2022 +0900

    or1k: Define PI_STATIC_AND_HIDDEN
    
    PI_STATIC_AND_HIDDEN means that references to static functions, data
    and symbols with hidden visibility do not need any run-time relocations
    after the final link, with the build flags used by glibc.
    
    OpenRISC follows this so enabled PI_STATIC_AND_HIDDEN by adding
    configure.ac and generating configure.
    
    Suggested-by: Florian Weimer <fweimer@redhat.com>

Diff:
---
 sysdeps/or1k/configure    | 5 +++++
 sysdeps/or1k/configure.ac | 4 ++++
 2 files changed, 9 insertions(+)

diff --git a/sysdeps/or1k/configure b/sysdeps/or1k/configure
new file mode 100644
index 0000000000..1fe508c447
--- /dev/null
+++ b/sysdeps/or1k/configure
@@ -0,0 +1,5 @@
+# This file is generated from configure.ac by Autoconf.  DO NOT EDIT!
+ # Local configure fragment for sysdeps/or1k.
+
+$as_echo "#define PI_STATIC_AND_HIDDEN 1" >>confdefs.h
+
diff --git a/sysdeps/or1k/configure.ac b/sysdeps/or1k/configure.ac
new file mode 100644
index 0000000000..76ff97dc9a
--- /dev/null
+++ b/sysdeps/or1k/configure.ac
@@ -0,0 +1,4 @@
+GLIBC_PROVIDES dnl See aclocal.m4 in the top level source directory.
+# Local configure fragment for sysdeps/or1k.
+
+AC_DEFINE(PI_STATIC_AND_HIDDEN)


                 reply	other threads:[~2022-02-02 11:05 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=20220202110537.038853858D1E@sourceware.org \
    --to=shorne@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).