mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: musl@lists.openwall.com
Cc: 1068350@bugs.debian.org
Subject: [musl] Re: Bug#1068350: musl: miscompiles (runtime problems) on riscv64 and s390x with static-pie
Date: Thu, 4 Apr 2024 19:50:40 +0000 (UTC)	[thread overview]
Message-ID: <Pine.BSM.4.64L.2404041942130.18654@herc.mirbsd.org> (raw)
In-Reply-To: <20240404105408.GB3766212@port70.net>

Szabolcs Nagy dixit:

>the next culprit is gcc (each target can have their own

gcc-13_13.2.0-23

>static pie specs) or the way you invoked gcc (not visible

As I wrote earlier, though with more flags. Dropping all the -D…
and -W… and -I… and other irrelevant ones:

musl-gcc -Os -g -fPIE -fno-lto -fno-asynchronous-unwind-tables
    -fno-strict-aliasing -fstack-protector-strong -fwrapv -c …
musl-gcc -Os -g -fPIE -fno-lto -fno-asynchronous-unwind-tables
    -fno-strict-aliasing -fstack-protector-strong -fwrapv
    -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -static -static-pie
    -fno-lto -o mksh  *.o

Same for both. You can see the full log by activating the
[64]Installed and [71]Installed links respectively on
https://buildd.debian.org/status/package.php?p=mksh and
skipping to 'compilation of mksh in static-musl' to get to
the beginning of the configure phase for that.

>are you sure static pie works on these targets?

No ;-) That’s why I reported this issue. I had just
enabled it for the musl builds, as the security people
like that more than normal static.

Thanks for looking,
//mirabilos
-- 
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
	-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc

  reply	other threads:[~2024-04-04 19:55 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 " Thorsten Glaser
2024-04-04 10:44   ` Szabolcs Nagy
2024-04-04 10:54     ` Szabolcs Nagy
2024-04-04 19:50       ` Thorsten Glaser [this message]
2024-04-04 20:26         ` [musl] Re: Bug#1068350: musl: miscompiles (runtime problems) on riscv64 and " 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
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.2404041942130.18654@herc.mirbsd.org \
    --to=tg@mirbsd.de \
    --cc=1068350@bugs.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).