public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wdijkstr at arm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29648] New: Static-pie builds contain many redundant GOT references
Date: Mon, 03 Oct 2022 15:40:06 +0000 [thread overview]
Message-ID: <bug-29648-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29648
Bug ID: 29648
Summary: Static-pie builds contain many redundant GOT
references
Product: glibc
Version: 2.35
Status: NEW
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: wdijkstr at arm dot com
CC: carlos at redhat dot com
Target Milestone: ---
The static-pie changes introduced ~1200 unnecessary GOT references in the
lib/*.a files. Even --disable-default-pie results in ~288 GOT references. GLIBC
2.34 and earlier contain zero GOT accesses as expected.
One issue is that "hidden" attributes are ignored with static-pie, which
results in codequality of the static-pie build being worse than fPIC...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-03 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 15:40 wdijkstr at arm dot com [this message]
2022-11-08 14:25 ` [Bug build/29648] " schwab@linux-m68k.org
2022-11-08 14:33 ` wdijkstr at arm dot com
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=bug-29648-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).