From: Florian Weimer <fweimer@redhat.com>
To: Stafford Horne <shorne@gmail.com>
Cc: GLIBC patches <libc-alpha@sourceware.org>,
Openrisc <openrisc@lists.librecores.org>
Subject: Re: [OpenRISC] [PATCH v5 00/13] Glibc OpenRISC port
Date: Mon, 24 Jan 2022 14:23:07 +0100 [thread overview]
Message-ID: <87tudt2rpg.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220104031414.2416928-1-shorne@gmail.com> (Stafford Horne's message of "Tue, 4 Jan 2022 12:14:01 +0900")
* Stafford Horne:
> This is the OpenRISC port for glibc that I have been working on.
The port does not define PI_STATIC_AND_HIDDEN. Is this really
necessary, or just an oversight due to the way the port was constructed
(presumably with MIPS as the template)?
PI_STATIC_AND_HIDDEN means that references to static functions and data
and symbols with hidden visibility do not need any run-time relocations
after the final link, with the build flags used by glibc.
Thanks,
Florian
next prev parent reply other threads:[~2022-01-24 13:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 3:14 Stafford Horne
2022-01-04 3:14 ` [PATCH v5 01/13] elf: Add reloc for OpenRISC Stafford Horne
2022-01-04 3:14 ` [PATCH v5 02/13] linux/syscalls: Add or1k_atomic syscall " Stafford Horne
2022-01-04 3:14 ` [PATCH v5 03/13] or1k: ABI Implementation Stafford Horne
2022-01-04 3:14 ` [PATCH v5 04/13] or1k: startup and dynamic linking code Stafford Horne
2022-01-04 3:14 ` [PATCH v5 05/13] or1k: Thread Local Storage support Stafford Horne
2022-01-04 3:14 ` [PATCH v5 06/13] or1k: Atomics and Locking primitives Stafford Horne
2022-01-04 3:14 ` [PATCH v5 07/13] or1k: math soft float support Stafford Horne
2022-01-04 3:14 ` [PATCH v5 08/13] or1k: Linux Syscall Interface Stafford Horne
2022-01-04 3:14 ` [PATCH v5 09/13] or1k: Linux ABI Stafford Horne
2022-01-04 3:14 ` [PATCH v5 10/13] or1k: ABI lists Stafford Horne
2022-01-04 12:27 ` Adhemerval Zanella
2022-01-04 21:37 ` Stafford Horne
2022-01-04 3:14 ` [PATCH v5 11/13] or1k: Build Infrastructure Stafford Horne
2022-01-04 3:14 ` [PATCH v5 12/13] build-many-glibcs.py: add OpenRISC support Stafford Horne
2022-01-04 3:14 ` [PATCH v5 13/13] Documentation for OpenRISC port Stafford Horne
2022-01-04 12:28 ` Adhemerval Zanella
2022-01-04 21:38 ` Stafford Horne
2022-01-04 12:34 ` [PATCH v5 00/13] Glibc " Adhemerval Zanella
2022-01-04 21:36 ` Stafford Horne
2022-01-05 21:34 ` [PATCH v5 00/13] Glibc OpenRISC port - PUSHED Stafford Horne
2022-01-24 13:23 ` Florian Weimer [this message]
2022-01-24 13:54 ` [OpenRISC] [PATCH v5 00/13] Glibc OpenRISC port Adhemerval Zanella
2022-01-25 1:19 ` Stafford Horne
2022-01-25 17:07 ` Adhemerval Zanella
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=87tudt2rpg.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.com \
/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).