From: Nathan Chancellor <nathan@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>, x86@kernel.org
Cc: "Rae Moar" <rmoar@google.com>,
"Sergio González Collado" <sergio.collado@gmail.com>,
"David Gow" <davidgow@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
"Nathan Chancellor" <nathan@kernel.org>
Subject: [PATCH] x86/tools: Drop unlikely definition from insn_decoder_test
Date: Tue, 18 Mar 2025 15:32:30 -0700 [thread overview]
Message-ID: <20250318-x86-decoder-test-fix-unlikely-redef-v1-1-74c84a7bf05b@kernel.org> (raw)
After commit c104c16073b7 ("Kunit to check the longest symbol length"),
there is a warning when building with clang because there is now a
definition of unlikely from compiler.h in tools/include/linux, which
conflicts with the one in the instruction decoder selftest.
arch/x86/tools/insn_decoder_test.c:15:9: warning: 'unlikely' macro redefined [-Wmacro-redefined]
15 | #define unlikely(cond) (cond)
| ^
tools/include/linux/compiler.h:128:10: note: previous definition is here
128 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
1 warning generated.
Remove the second unlikely definition, as it is no longer necessary,
clearing up the warning.
Fixes: c104c16073b7 ("Kunit to check the longest symbol length")
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
---
arch/x86/tools/insn_decoder_test.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/tools/insn_decoder_test.c b/arch/x86/tools/insn_decoder_test.c
index 6c2986d2ad11..08cd913cbd4e 100644
--- a/arch/x86/tools/insn_decoder_test.c
+++ b/arch/x86/tools/insn_decoder_test.c
@@ -12,8 +12,6 @@
#include <stdarg.h>
#include <linux/kallsyms.h>
-#define unlikely(cond) (cond)
-
#include <asm/insn.h>
#include <inat.c>
#include <insn.c>
---
base-commit: 2e0cf2b32f72b20b0db5cc665cd8465d0f257278
change-id: 20250318-x86-decoder-test-fix-unlikely-redef-1636897e4fe7
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
next reply other threads:[~2025-03-18 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 22:32 Nathan Chancellor [this message]
2025-03-19 20:31 ` Ingo Molnar
2025-03-28 21:06 ` Shuah Khan
2025-03-28 21:56 ` Ingo Molnar
2025-03-28 22:04 ` [tip: x86/urgent] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c tip-bot2 for Nathan Chancellor
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=20250318-x86-decoder-test-fix-unlikely-redef-v1-1-74c84a7bf05b@kernel.org \
--to=nathan@kernel.org \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=rmoar@google.com \
--cc=sergio.collado@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®