From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/nolibc: stop testing constructor order
Date: Thu, 6 Mar 2025 23:21:21 +0100 [thread overview]
Message-ID: <20250306222121.GA697@1wt.eu> (raw)
In-Reply-To: <20250306-nolibc-constructor-order-v1-1-68fd161cc5ec@weissschuh.net>
On Thu, Mar 06, 2025 at 10:52:39PM +0100, Thomas Weißschuh wrote:
> The execution order of constructors in undefined and depends on the
> toolchain. While recent toolchains seems to have a stable order, it
> doesn't work for older ones and may also change at any time.
>
> Stop validating the order and instead only validate that all
> constructors are executed.
>
> Reported-by: Willy Tarreau <w@1wt.eu>
> Closes: https://lore.kernel.org/lkml/20250301110735.GA18621@1wt.eu/
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Awesome, thank you very much, Thomas!
Willy
prev parent reply other threads:[~2025-03-06 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 21:52 [PATCH] selftests/nolibc: stop testing constructor order Thomas Weißschuh
2025-03-06 22:21 ` Willy Tarreau [this message]
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=20250306222121.GA697@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.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