SUPERH platform development
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "Michael.Karcher" <Michael.Karcher@fu-berlin.de>,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: jakub@gcc.gnu.org
Subject: Re: [PATCH: 1/1] sh4: avoid spurious gcc warning
Date: Sun, 22 Jan 2023 13:35:21 +0100	[thread overview]
Message-ID: <eee8f8c8-6a5a-4ec3-e1e7-1103da7bb7ae@physik.fu-berlin.de> (raw)
In-Reply-To: <52952170-f1a9-89a0-e307-f974ce2b7977@fu-berlin.de>

Hi Michael!

On 1/22/23 01:15, Michael.Karcher wrote:
> Prevent sizeof-pointer-div warning in SH4 intc macros
> 
> Gcc warns about the pattern sizeof(void*)/sizeof(void), as it looks like
> the abuse of a pattern to calculate the array size. This pattern appears
> in the unevaluated part of the ternary operator in _INTC_ARRAY if the
> parameter is NULL.
> 
> The replacement uses an alternate approach to return 0 in case of NULL
> which does not generate the pattern sizeof(void*)/sizeof(void), but still
> emits the warning if _INTC_ARRAY is called with a nonarray parameter.
> 
> This patch is required for successful compilation with -Werror enabled.
> 
> The idea to use _Generic for type distinction is taken from Comment #7
> in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108483 by Jakub Jelinek
> 
> Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>
> ---
> 
> diff --git a/include/linux/sh_intc.h b/include/linux/sh_intc.h
> index c255273b0281..d7a7ffb60a34 100644
> --- a/include/linux/sh_intc.h
> +++ b/include/linux/sh_intc.h
> @@ -97,7 +97,7 @@ struct intc_hw_desc {
>       unsigned int nr_subgroups;
>   };
> 
> -#define _INTC_ARRAY(a) a, __same_type(a, NULL) ? 0 : sizeof(a)/sizeof(*a)
> +#define _INTC_ARRAY(a) a, sizeof(a)/(_Generic((a), typeof(NULL): 0xFFFFFFFFU, default: sizeof(*a)))
> 
>   #define INTC_HW_DESC(vectors, groups, mask_regs,    \
>                prio_regs,    sense_regs, ack_regs)    \

The title should probably be "arch/sh: avoid spurious gcc warning" since it's not
a problem special to sh4 but affects the whole arch/sh sub-folder which covers
all SuperH and J-Core targets.

Can you rephrase the title accordingly?

Adrian

-- 
  .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


  parent reply	other threads:[~2023-01-22 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22  0:15 [PATCH: 1/1] sh4: avoid spurious gcc warning Michael.Karcher
2023-01-22  7:00 ` Randy Dunlap
2023-01-22 11:33   ` Michael Karcher
2023-01-22 12:42     ` Jakub Jelinek
2023-01-22 16:02       ` Randy Dunlap
2023-01-23 14:49       ` Geert Uytterhoeven
2023-01-22 12:35 ` John Paul Adrian Glaubitz [this message]
     [not found] ` <c411961861df4ae4b011317ff2c3c7df@AcuMS.aculab.com>
2023-01-23 16:11   ` Jakub Jelinek
2023-01-23 18:00     ` Michael Karcher

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=eee8f8c8-6a5a-4ec3-e1e7-1103da7bb7ae@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=Michael.Karcher@fu-berlin.de \
    --cc=dalias@libc.org \
    --cc=jakub@gcc.gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=segher@kernel.crashing.org \
    --cc=ysato@users.sourceforge.jp \
    /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