From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "Michael.Karcher" <Michael.Karcher@fu-berlin.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-xtensa@linux-xtensa.org, Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-mips@vger.kernel.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
linux-f2fs-devel@lists.sourceforge.net,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [f2fs-dev] Calculating array sizes in C - was: Re: Build regressions/improvements in v6.2-rc1
Date: Fri, 20 Jan 2023 09:49:00 +0100 [thread overview]
Message-ID: <c1d233b9-bc85-dce9-ffa0-eb3170602c6c@physik.fu-berlin.de> (raw)
In-Reply-To: <1732342f-49fe-c20e-b877-bc0a340e1a50@fu-berlin.de>
Hi Michael!
On 1/19/23 23:11, Michael.Karcher wrote:
> I suggest to file a bug against gcc complaining about a "spurious warning",
> and using "-Werror -Wno-error-sizeof-pointer-div" until gcc is adapted to
> not emit the warning about the pointer division if the result is not used.
Could you post a kernel patch for that? I would be happy to test it on my
SH-7785CLR board. Also, I'm going to file a bug report against GCC.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-01-20 8:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgf929uGOVpiWALPyC7pv_9KbwB2EAvQ3C4woshZZ5zqQ@mail.gmail.com>
[not found] ` <20221227082932.798359-1-geert@linux-m68k.org>
[not found] ` <alpine.DEB.2.22.394.2212270933530.311423@ramsan.of.borg>
2023-01-06 15:10 ` [f2fs-dev] Build regressions/improvements in v6.2-rc1 John Paul Adrian Glaubitz
2023-01-06 15:17 ` Geert Uytterhoeven
2023-01-06 15:18 ` Geert Uytterhoeven
2023-01-17 16:42 ` [f2fs-dev] Calculating array sizes in C - was: " John Paul Adrian Glaubitz
2023-01-17 17:01 ` Geert Uytterhoeven
2023-01-17 17:06 ` John Paul Adrian Glaubitz
2023-01-17 20:05 ` Geert Uytterhoeven
2023-01-17 20:37 ` John Paul Adrian Glaubitz
2023-01-19 22:11 ` Michael.Karcher
2023-01-20 3:31 ` Rob Landley
2023-01-20 10:53 ` Segher Boessenkool
2023-01-20 11:42 ` David Laight
2023-01-20 18:29 ` Michael.Karcher
2023-01-20 8:49 ` John Paul Adrian Glaubitz [this message]
[not found] ` <def16c9b-7bb1-a454-0896-b063a9e85964@fu-berlin.de>
2023-01-21 21:26 ` John Paul Adrian Glaubitz
2023-01-06 15:39 ` [f2fs-dev] " Alex Deucher
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=c1d233b9-bc85-dce9-ffa0-eb3170602c6c@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=Michael.Karcher@fu-berlin.de \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=kasan-dev@googlegroups.com \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).