From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sandbox:stable-2.x commit in: tests/
Date: Mon, 11 Nov 2024 22:48:39 +0000 (UTC) [thread overview]
Message-ID: <1731365316.d37d82ff00bc2e4b0a10b50679f5233e0d056cb7.sam@gentoo> (raw)
commit: d37d82ff00bc2e4b0a10b50679f5233e0d056cb7
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 11 10:33:42 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Nov 11 22:48:36 2024 +0000
URL: https://gitweb.gentoo.org/proj/sandbox.git/commit/?id=d37d82ff
tests: handle traps on NULL input for utimensat
When building with -fisolate-erroneous-paths-attribute, GCC turns
the call to utimensat w/ a NULL arg into a trap because of its nonnull
attribute(s). Workaround that in the test.
Bug: https://bugs.gentoo.org/549108
Signed-off-by: Sam James <sam <AT> gentoo.org>
(cherry picked from commit b8a6ddb6fc1832abc1b396f285b864858bb18026)
tests/utimensat-0.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/tests/utimensat-0.c b/tests/utimensat-0.c
index 99c3fa4..4e8b89c 100644
--- a/tests/utimensat-0.c
+++ b/tests/utimensat-0.c
@@ -1,3 +1,6 @@
+#pragma GCC push_options
+#pragma GCC optimize("-fno-isolate-erroneous-paths-dereference,-fno-isolate-erroneous-paths-attribute")
+
#define CONFIG HAVE_UTIMENSAT
#define FUNC utimensat
#define SFUNC "utimensat"
@@ -20,3 +23,5 @@
int flags = at_get_flags(s);
#include "test-skel-0.c"
+
+#pragma GCC pop_options
next reply other threads:[~2024-11-11 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 22:48 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-08 4:09 [gentoo-commits] proj/sandbox:stable-2.x commit in: tests/ Mike Gilbert
2025-01-08 3:29 Mike Gilbert
2025-01-08 3:04 Mike Gilbert
2023-07-01 23:54 Mike Gilbert
2023-06-22 13:55 Mike Gilbert
2023-06-22 13:55 Mike Gilbert
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=1731365316.d37d82ff00bc2e4b0a10b50679f5233e0d056cb7.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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