From: Nick Alcock <nick.alcock@oracle.com>
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH 4/5] test: tid_pid: don't assume the type of pthread_t
Date: Mon, 6 Oct 2025 16:28:27 +0100 [thread overview]
Message-ID: <20251006152829.239100-4-nick.alcock@oracle.com> (raw)
In-Reply-To: <20251006152829.239100-1-nick.alcock@oracle.com>
GCC 16 warns about this mismatch.
Signed-off-by: Nick Alcock <nick.alcock@oracle.com>
---
test/unittest/builtinvar/tst.tid_pid.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/unittest/builtinvar/tst.tid_pid.sh b/test/unittest/builtinvar/tst.tid_pid.sh
index e367411dcfb7d..7551f7c4b8f5c 100755
--- a/test/unittest/builtinvar/tst.tid_pid.sh
+++ b/test/unittest/builtinvar/tst.tid_pid.sh
@@ -51,7 +51,7 @@ int main(int c, char **v) {
pthread_create(&mythr, NULL, &foo, NULL);
/* Also report the pthread_t. */
- printf("created pthread_t %lld\n\n", mythr);
+ printf("created pthread_t %llu\n\n", (long long unsigned) mythr);
fflush(stdout);
/* Wait endlessly. DTrace will kill me when it is done. */
--
2.51.0.284.g117bcb8de7
next prev parent reply other threads:[~2025-10-06 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 15:28 [PATCH 1/5] test: fbt return0: work on quiet systems Nick Alcock
2025-10-06 15:28 ` [PATCH 2/5] test: nfs: don't require a locking daemon Nick Alcock
2025-10-06 16:11 ` Kris Van Hees
2025-10-06 15:28 ` [PATCH 3/5] test: preprocessor: work on GCC 16 Nick Alcock
2025-10-07 15:08 ` Kris Van Hees
2025-10-06 15:28 ` Nick Alcock [this message]
2025-10-06 16:13 ` [PATCH 4/5] test: tid_pid: don't assume the type of pthread_t Kris Van Hees
2025-10-06 15:28 ` [PATCH 5/5] test: dupstruct: fix extra duplicate identifier case Nick Alcock
2025-10-06 16:14 ` Kris Van Hees
2025-10-06 16:09 ` [PATCH 1/5] test: fbt return0: work on quiet systems Kris Van Hees
2025-10-07 15:36 ` Nick Alcock
2025-10-08 11:16 ` [PATCH v2 " Nick Alcock
2025-10-08 16:15 ` Kris Van Hees
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=20251006152829.239100-4-nick.alcock@oracle.com \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
/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