From: Carlos Llamas <cmllamas@google.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Colin Ian King <colin.i.king@gmail.com>,
Valentin Obst <kernel@valentinobst.de>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH v2] selftests/vDSO: fix clang build errors and warnings
Date: Tue, 11 Jun 2024 18:30:00 +0000 [thread overview]
Message-ID: <ZmiXqOHYaLLX557z@google.com> (raw)
In-Reply-To: <20240527211622.290635-1-jhubbard@nvidia.com>
On Mon, May 27, 2024 at 02:16:22PM -0700, John Hubbard wrote:
> When building with clang, via:
>
> make LLVM=1 -C tools/testing/selftests
>
> ...there are several warnings, and an error. This fixes all of those and
> allows these tests to run and pass.
It might be best to split the 4 _different_ fixes into separate patches.
>
> 1. Fix linker error (undefined reference to memcpy) by providing a local
> version of memcpy.
>
> 2. clang complains about using this form:
>
> if (g = h & 0xf0000000)
>
> ...so factor out the assignment into a separate step.
There has been multiple attempts to fix this. I can see these two:
https://lore.kernel.org/all/20211206102931.1433871-1-anders.roxell@linaro.org/
https://lore.kernel.org/all/20240501002150.1370861-1-edliaw@google.com/
... I guess we somehow missed those?
>
> 3. The code is passing a signed const char* to elf_hash(), which expects
> a const unsigned char *. There are several callers, so fix this at
> the source by allowing the function to accept a signed argument, and
> then converting to unsigned operations, once inside the function.
>
There is also a v4 fix for this item that was sent out here:
https://lore.kernel.org/all/20240506181951.1804451-1-edliaw@google.com/
> 4. clang doesn't have __attribute__((externally_visible)) and generates
> a warning to that effect. Fortunately, gcc 12 and gcc 13 do not seem
> to require that attribute in order to build, run and pass tests here,
> so remove it.
>
> [1] https://lore.kernel.org/all/20240329-selftests-libmk-llvm-rfc-v1-1-2f9ed7d1c49f@valentinobst.de/
What is this about? Left over from v1 maybe?
>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
I would prefer to pick up the fixes from folks who sent out the patches
first but I'm fine either way.
Reviewed-by: Carlos Llamas <cmllamas@google.com>
next prev parent reply other threads:[~2024-06-11 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 21:16 [PATCH v2] selftests/vDSO: fix clang build errors and warnings John Hubbard
2024-05-29 8:05 ` Muhammad Usama Anjum
2024-05-30 19:24 ` John Hubbard
2024-06-04 21:18 ` [v2] " Edward Liaw
2024-06-11 18:30 ` Carlos Llamas [this message]
2024-06-14 22:51 ` [PATCH v2] " John Hubbard
2024-06-14 22:56 ` John Hubbard
2024-06-14 23:10 ` Carlos Llamas
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=ZmiXqOHYaLLX557z@google.com \
--to=cmllamas@google.com \
--cc=broonie@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=shuah@kernel.org \
--cc=vincenzo.frascino@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.