From: Ian Rogers <irogers@google.com>
To: Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Arnd Bergmann <arnd@arndb.de>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jakub Kicinski <kuba@kernel.org>,
Jacob Keller <jacob.e.keller@intel.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: [PATCH v1 0/5] Silence some clang -Wshorten-64-to-32 warnings
Date: Thu, 3 Apr 2025 09:56:57 -0700 [thread overview]
Message-ID: <20250403165702.396388-1-irogers@google.com> (raw)
Clang's shorten-64-to-32 can be useful to spot certain kinds of bugs
that can be more prevalent in C code due to implicit 64 to 32-bit
casting. Add some explicit casts to header files so as to avoid the
warning when these headers are used.
This patch started out as a single patch in a series for the perf tool
where a bug could have been identified were -Wshorten-64-to-32
enabled:
https://lore.kernel.org/lkml/20250401182347.3422199-3-irogers@google.com/
Ian Rogers (5):
bitfield: Silence a clang -Wshorten-64-to-32 warning
bitmap: Silence a clang -Wshorten-64-to-32 warning
bitops: Silence a clang -Wshorten-64-to-32 warning
math64: Silence a clang -Wshorten-64-to-32 warning
hash.h: Silence a clang -Wshorten-64-to-32 warning
include/asm-generic/bitops/fls64.h | 2 +-
include/linux/bitfield.h | 2 +-
include/linux/bitmap.h | 2 +-
include/linux/hash.h | 2 +-
include/linux/math64.h | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
--
2.49.0.504.g3bcea36a83-goog
next reply other threads:[~2025-04-03 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 16:56 Ian Rogers [this message]
2025-04-03 16:56 ` [PATCH v1 1/5] bitfield: Silence a clang -Wshorten-64-to-32 warning Ian Rogers
2025-04-03 16:56 ` [PATCH v1 2/5] bitmap: " Ian Rogers
2025-04-04 5:49 ` Arnd Bergmann
2025-04-04 11:31 ` Ian Rogers
2025-04-03 16:57 ` [PATCH v1 3/5] bitops: " Ian Rogers
2025-04-04 5:43 ` Arnd Bergmann
2025-04-04 11:35 ` Ian Rogers
2025-04-03 16:57 ` [PATCH v1 4/5] math64: " Ian Rogers
2025-04-03 16:57 ` [PATCH v1 5/5] hash.h: " Ian Rogers
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=20250403165702.396388-1-irogers@google.com \
--to=irogers@google.com \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=jacob.e.keller@intel.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=tglx@linutronix.de \
--cc=yury.norov@gmail.com \
/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