From: Ammar Faizi <[email protected]>
To: GNU/Weeb Mailing List <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Nick Mathewson <[email protected]>
Subject: [PATCH tor v1 5/6] test/bench: Fix clang-15 complaint (unused variable)
Date: Thu, 26 May 2022 18:41:29 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
clang-15 throws the following complaint:
```
src/test/bench.c:380:14: error: variable 't' set but not used [-Werror,-Wunused-but-set-variable]
uint32_t t=0;
^
1 error generated.
```
This variable firstly introduced in commit 490e187056d8 ("Add a
benchmark for our several PRNGs."). Suppress the complaint by
casting it to `(void)`.
Cc: Nick Mathewson <[email protected]>
Signed-off-by: Ammar Faizi <[email protected]>
---
src/test/bench.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/test/bench.c b/src/test/bench.c
index a76ea67eb8..8a4a998e8d 100644
--- a/src/test/bench.c
+++ b/src/test/bench.c
@@ -381,6 +381,7 @@ bench_rand_len(int len)
for (i = 0; i < N; ++i) {
t += tor_weak_random(&weak);
}
+ (void)t;
end = perftime();
printf("weak_rand(4): %f nsec.\n", NANOCOUNT(start,end,N));
}
--
Ammar Faizi
next prev parent reply other threads:[~2022-05-26 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 11:41 [GIT PULL tor v1 0/6] Build fixes for clang-15 Ammar Faizi
2022-05-26 11:41 ` [PATCH tor v1 1/6] channel: Fix clang-15 complaint (unused variable) Ammar Faizi
2022-05-26 11:41 ` [PATCH tor v1 2/6] connection_or: " Ammar Faizi
2022-05-26 11:41 ` [PATCH tor v1 3/6] routerlist: " Ammar Faizi
2022-05-26 11:41 ` [PATCH tor v1 4/6] compat_libevent: " Ammar Faizi
2022-05-26 11:41 ` Ammar Faizi [this message]
2022-05-26 11:41 ` [PATCH tor v1 6/6] test/test_hs_descriptor: Don't invoke GCC warning when compiling with clang Ammar Faizi
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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