public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Shuah Khan <shuah@kernel.org>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Bill Wendling" <morbo@google.com>,
	"Justin Stitt" <justinstitt@google.com>,
	"Fenghua Yu" <fenghua.yu@intel.com>,
	"Reinette Chatre" <reinette.chatre@intel.com>,
	"Valentin Obst" <kernel@valentinobst.de>,
	linux-kselftest@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	llvm@lists.linux.dev,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH] selftests/resctrl: fix clang build warnings related to abs(), labs() calls
Date: Wed, 8 May 2024 12:39:53 -0700	[thread overview]
Message-ID: <8ee4ae34-dd65-4d23-a7fb-883603780f06@nvidia.com> (raw)
In-Reply-To: <20240508190254.266892-1-jhubbard@nvidia.com>

This was supposed to be a v3 patch. I'll resend as v3, sorry
about creating a confusing email here.

thanks,
-- 
John Hubbard
NVIDIA

On 5/8/24 12:02 PM, John Hubbard wrote:
> When building with clang, via:
> 
>      make LLVM=1 -C tools/testing/selftests
> 
> ...two types of warnings occur:
> 
>      warning: absolute value function 'abs' given an argument of type
>      'long' but has parameter of type 'int' which may cause truncation of
>      value
> 
>      warning: taking the absolute value of unsigned type 'unsigned long'
>      has no effect
> 
> Fix these by:
> 
> a) using labs() in place of abs(), when long integers are involved, and
> 
> b) Change to use signed integer data types, in places where subtraction
>     is used (and could end up with negative values).
> 
> c) Remove a duplicate abs() call in cmt_test.c.
> 
> Cc: Reinette Chatre <reinette.chatre@intel.com>
> Cc: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
>   tools/testing/selftests/resctrl/cmt_test.c | 4 ++--
>   tools/testing/selftests/resctrl/mba_test.c | 2 +-
>   tools/testing/selftests/resctrl/mbm_test.c | 2 +-
>   3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/testing/selftests/resctrl/cmt_test.c b/tools/testing/selftests/resctrl/cmt_test.c
> index a81f91222a89..05a241519ae8 100644
> --- a/tools/testing/selftests/resctrl/cmt_test.c
> +++ b/tools/testing/selftests/resctrl/cmt_test.c
> @@ -40,11 +40,11 @@ static int show_results_info(unsigned long sum_llc_val, int no_of_bits,
>   	int ret;
>   
>   	avg_llc_val = sum_llc_val / num_of_runs;
> -	avg_diff = (long)abs(cache_span - avg_llc_val);
> +	avg_diff = (long)(cache_span - avg_llc_val);
>   	diff_percent = ((float)cache_span - avg_llc_val) / cache_span * 100;
>   
>   	ret = platform && abs((int)diff_percent) > max_diff_percent &&
> -	      abs(avg_diff) > max_diff;
> +	      labs(avg_diff) > max_diff;
>   
>   	ksft_print_msg("%s Check cache miss rate within %lu%%\n",
>   		       ret ? "Fail:" : "Pass:", max_diff_percent);
> diff --git a/tools/testing/selftests/resctrl/mba_test.c b/tools/testing/selftests/resctrl/mba_test.c
> index 7946e32e85c8..5fffbc9ff6a4 100644
> --- a/tools/testing/selftests/resctrl/mba_test.c
> +++ b/tools/testing/selftests/resctrl/mba_test.c
> @@ -60,7 +60,7 @@ static bool show_mba_info(unsigned long *bw_imc, unsigned long *bw_resc)
>   	/* Memory bandwidth from 100% down to 10% */
>   	for (allocation = 0; allocation < ALLOCATION_MAX / ALLOCATION_STEP;
>   	     allocation++) {
> -		unsigned long avg_bw_imc, avg_bw_resc;
> +		long avg_bw_imc, avg_bw_resc;
>   		unsigned long sum_bw_imc = 0, sum_bw_resc = 0;
>   		int avg_diff_per;
>   		float avg_diff;
> diff --git a/tools/testing/selftests/resctrl/mbm_test.c b/tools/testing/selftests/resctrl/mbm_test.c
> index d67ffa3ec63a..a4c3ea49b0e8 100644
> --- a/tools/testing/selftests/resctrl/mbm_test.c
> +++ b/tools/testing/selftests/resctrl/mbm_test.c
> @@ -17,7 +17,7 @@
>   static int
>   show_bw_info(unsigned long *bw_imc, unsigned long *bw_resc, size_t span)
>   {
> -	unsigned long avg_bw_imc = 0, avg_bw_resc = 0;
> +	long avg_bw_imc = 0, avg_bw_resc = 0;
>   	unsigned long sum_bw_imc = 0, sum_bw_resc = 0;
>   	int runs, ret, avg_diff_per;
>   	float avg_diff = 0;
> 
> base-commit: 45db3ab70092637967967bfd8e6144017638563c
> prerequisite-patch-id: b901ece2a5b78503e2fb5480f20e304d36a0ea27
> prerequisite-patch-id: 8d96c4b8c3ed6d9ea2588ef7f594ae0f9f83c279



  reply	other threads:[~2024-05-08 19:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 19:02 [PATCH] selftests/resctrl: fix clang build warnings related to abs(), labs() calls John Hubbard
2024-05-08 19:39 ` John Hubbard [this message]
2024-05-10  9:06 ` Ilpo Järvinen
2024-05-10 18:01   ` John Hubbard
  -- strict thread matches above, loose matches on Subject: below --
2024-05-03  2:32 John Hubbard
2024-05-03  8:00 ` Ilpo Järvinen
2024-05-03 16:52   ` John Hubbard
2024-05-03 18:37     ` Reinette Chatre
2024-05-03 19:12       ` John Hubbard
2024-05-03 20:46         ` Reinette Chatre
2024-05-03 22:00           ` John Hubbard
2024-05-06  9:07         ` Ilpo Järvinen
2024-05-06 17:21           ` John Hubbard

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=8ee4ae34-dd65-4d23-a7fb-883603780f06@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=fenghua.yu@intel.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=justinstitt@google.com \
    --cc=kernel@valentinobst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=reinette.chatre@intel.com \
    --cc=shuah@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