From: Thorsten Glaser <tg@mirbsd.de>
To: musl@lists.openwall.com
Cc: 1068350@bugs.debian.org, debian-glibc@lists.debian.org, doko@debian.org
Subject: Re: [musl] Re: Bug#1068350: musl: miscompiles (runtime problems) on riscv64 and s390x with static-pie → seems to be a toolchain bug after all, it does too hit glibc
Date: Fri, 5 Apr 2024 05:58:15 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.2404050555120.14283@herc.mirbsd.org> (raw)
In-Reply-To: <Zg-MykEfuqBWpAOY@voyager>
Markus Wichmann dixit:
>I may not really know what I am talking about, so take this with a grain
>of salt, but isn't this missing a -Bsymbolic somewhere? Ironically, that
>switch causes ld to not emit symbolic relocations. I seem to remember
>reading long ago in Rich's initial -static-pie proposal that that was
>one of the switches added to the linker command line.
When searching for which architectures support static PIE in the first
place (sadly, there doesn’t seem a consistent list), I found one saying
it’s no longer necessart after some point, so I didn’t check it.
>In any case, the emission of non-relative relocations is the issue here,
>and it is coming from the linker.
They are present in the glibc static-pie binary as well, though.
And tbh they look to me like “just plug the absolute address of
the symbol here, please”, which is perfectly fine for things like
an array of strings when the actual string has already its own symbol.
(Disclaimer: I know… barely anything about Unix relocation types,
a bit more about those on DOS and even TOS.)
bye,
//mirabilos
--
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival
next prev parent reply other threads:[~2024-04-05 6:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171218457890.157989.17235252523998125898.reportbug@zelenka.debian.org>
2024-04-03 23:57 ` [musl] Re: Bug#1068350: musl: miscompiles (runtime problems) on s390x with static-pie Thorsten Glaser
2024-04-04 10:44 ` Szabolcs Nagy
2024-04-04 10:54 ` Szabolcs Nagy
2024-04-04 19:50 ` [musl] Re: Bug#1068350: musl: miscompiles (runtime problems) on riscv64 and " Thorsten Glaser
2024-04-04 20:26 ` Rich Felker
2024-04-04 20:40 ` Thorsten Glaser
2024-04-04 21:18 ` [musl] Re: Bug#1068350: musl: miscompiles (runtime problems) on riscv64 and s390x with static-pie → seems to be a toolchain bug after all, it does too hit glibc Thorsten Glaser
2024-04-05 0:26 ` Thorsten Glaser
2024-04-05 4:11 ` Markus Wichmann
2024-04-05 5:04 ` Thorsten Glaser
2024-04-05 5:31 ` Markus Wichmann
2024-04-05 5:58 ` Thorsten Glaser [this message]
2024-04-05 6:42 ` Markus Wichmann
2024-04-05 6:48 ` Szabolcs Nagy
2024-04-06 3:00 ` Rich Felker
2024-04-06 15:18 ` Thorsten Glaser
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=Pine.BSM.4.64L.2404050555120.14283@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=1068350@bugs.debian.org \
--cc=debian-glibc@lists.debian.org \
--cc=doko@debian.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).