[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.23.453.2011251022550.14@nippy.intranet>
Date: Wed, 25 Nov 2020 10:53:13 +1100 (AEDT)
From: Finn Thain <fthain@...egraphics.com.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
cc: Kees Cook <keescook@...omium.org>,
James Bottomley <James.Bottomley@...senpartnership.com>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Joe Perches <joe@...ches.com>,
Jakub Kicinski <kuba@...nel.org>, alsa-devel@...a-project.org,
linux-atm-general@...ts.sourceforge.net,
reiserfs-devel@...r.kernel.org, linux-iio@...r.kernel.org,
linux-wireless <linux-wireless@...r.kernel.org>,
linux-fbdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Nathan Chancellor <natechancellor@...il.com>,
linux-ide@...r.kernel.org, dm-devel@...hat.com,
keyrings@...r.kernel.org, linux-mtd@...ts.infradead.org,
GR-everest-linux-l2@...vell.com, wcn36xx@...ts.infradead.org,
samba-technical@...ts.samba.org, linux-i3c@...ts.infradead.org,
linux1394-devel@...ts.sourceforge.net,
linux-afs@...ts.infradead.org,
usb-storage@...ts.one-eyed-alien.net, drbd-dev@...ts.linbit.com,
devel@...verdev.osuosl.org, linux-cifs@...r.kernel.org,
rds-devel@....oracle.com,
Nick Desaulniers <ndesaulniers@...gle.com>,
linux-scsi@...r.kernel.org, linux-rdma@...r.kernel.org,
oss-drivers@...ronome.com, bridge@...ts.linux-foundation.org,
linux-security-module@...r.kernel.org,
amd-gfx@...ts.freedesktop.org,
linux-stm32@...md-mailman.stormreply.com, cluster-devel@...hat.com,
linux-acpi@...r.kernel.org, coreteam@...filter.org,
intel-wired-lan@...ts.osuosl.org,
linux-input <linux-input@...r.kernel.org>,
Miguel Ojeda <ojeda@...nel.org>,
tipc-discussion@...ts.sourceforge.net,
Ext4 Developers List <linux-ext4@...r.kernel.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
linux-watchdog@...r.kernel.org, selinux@...r.kernel.org,
linux-arm-msm@...r.kernel.org, intel-gfx@...ts.freedesktop.org,
linux-geode@...ts.infradead.org, linux-can@...r.kernel.org,
linux-block@...r.kernel.org, linux-gpio@...r.kernel.org,
op-tee@...ts.trustedfirmware.org,
linux-mediatek@...ts.infradead.org, xen-devel@...ts.xenproject.org,
nouveau@...ts.freedesktop.org, linux-hams@...r.kernel.org,
ceph-devel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-hwmon@...r.kernel.org,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
linux-nfs@...r.kernel.org, GR-Linux-NIC-Dev@...vell.com,
Linux-MM <linux-mm@...ck.org>,
Network Development <netdev@...r.kernel.org>,
linux-decnet-user@...ts.sourceforge.net, linux-mmc@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, linux-sctp@...r.kernel.org,
linux-usb@...r.kernel.org, netfilter-devel@...r.kernel.org,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
patches@...nsource.cirrus.com, linux-integrity@...r.kernel.org,
target-devel@...r.kernel.org, linux-hardening@...r.kernel.org,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [Intel-wired-lan] [PATCH 000/141] Fix fall-through warnings for
Clang
On Wed, 25 Nov 2020, Miguel Ojeda wrote:
>
> The C standard has nothing to do with this. We use compiler extensions
> of several kinds, for many years. Even discounting those extensions, the
> kernel is not even conforming to C due to e.g. strict aliasing. I am not
> sure what you are trying to argue here.
>
I'm saying that supporting the official language spec makes more sense
than attempting to support a multitude of divergent interpretations of the
spec (i.e. gcc, clang, coverity etc.)
I'm also saying that the reason why we use -std=gnu89 is that existing
code was written in that language, not in ad hoc languages comprised of
collections of extensions that change with every release.
> But, since you insist: yes, the `fallthrough` attribute is in the
> current C2x draft.
>
Thank you for checking. I found a free version that's only 6 weeks old:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2583.pdf
It will be interesting to see whether 6.7.11.5 changes once the various
implementations reach agreement.
Powered by blists - more mailing lists