linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Arnd Bergmann <arnd@arndb.de>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: kbuild test robot <lkp@intel.com>,
	linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: use -fno-strict-aliasing for decompressor
Date: Fri, 8 May 2020 23:40:37 +0200	[thread overview]
Message-ID: <5849978b-7330-1dae-0896-7ecbc6083d34@gmx.de> (raw)
In-Reply-To: <20200508093553.2742898-1-arnd@arndb.de>

On 08.05.20 11:35, Arnd Bergmann wrote:
> An experimental patch series of mine reworks how warnings are processed
> in Kbuild. A side effect is a new warning about a harmless aliasing
> rule violation in an inline function:
>
> In file included from
> include/linux/rhashtable-types.h:15:0,
>                  from include/linux/ipc.h:7,
>                  from include/uapi/linux/sem.h:5,
>                  from include/linux/sem.h:5,
>                  from include/linux/sched.h:15,
>                  from include/linux/uaccess.h:6,
>                  from arch/parisc/boot/compressed/misc.c:7:
> include/linux/workqueue.h: In function 'work_static':
> include/linux/workqueue.h:212:2: warning: dereferencing
> type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
>   return *work_data_bits(work) & WORK_STRUCT_STATIC;
>
> Make the decompressor use -fno-strict-aliasing like the rest of
> the kernel for consistency, and to ensure this warning never makes
> it into a release.
>
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Acked-by: Helge Deller <deller@gmx.de>

Arnd, will you take it through your trees when you push your experimental
patches, or do you want me to take it through the parisc tree?

Helge

> ---
>  arch/parisc/boot/compressed/Makefile | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/parisc/boot/compressed/Makefile b/arch/parisc/boot/compressed/Makefile
> index 1e5879c6a752..dff453687530 100644
> --- a/arch/parisc/boot/compressed/Makefile
> +++ b/arch/parisc/boot/compressed/Makefile
> @@ -16,6 +16,7 @@ targets += real2.S firmware.c
>
>  KBUILD_CFLAGS := -D__KERNEL__ -O2 -DBOOTLOADER
>  KBUILD_CFLAGS += -DDISABLE_BRANCH_PROFILING
> +KBUILD_CFLAGS += -fno-strict-aliasing
>  KBUILD_CFLAGS += $(cflags-y) -fno-delete-null-pointer-checks -fno-builtin-printf
>  KBUILD_CFLAGS += -fno-PIE -mno-space-regs -mdisable-fpregs -Os
>  ifndef CONFIG_64BIT
>


  reply	other threads:[~2020-05-08 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  9:35 [PATCH] parisc: use -fno-strict-aliasing for decompressor Arnd Bergmann
2020-05-08 21:40 ` Helge Deller [this message]
2020-05-08 21:43   ` Arnd Bergmann

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=5849978b-7330-1dae-0896-7ecbc6083d34@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).