From: Arnd Bergmann <arnd@kernel.org>
To: john@quad.stoffel.home
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
llvm@lists.linux.dev, Jonathan Corbet <corbet@lwn.net>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Alex Shi <alexs@kernel.org>, Hu Haowen <src.res@email.cn>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-doc-tw-discuss@lists.sourceforge.net,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Kbuild: remove -std=gnu89 from compiler arguments
Date: Mon, 28 Feb 2022 09:11:37 +0100 [thread overview]
Message-ID: <CAK8P3a1A8Y3F93FzbWum9U=_Mc8zR9T5p=tTkQK90ARan41EbA@mail.gmail.com> (raw)
In-Reply-To: <YhwT2Gw8vsQHPxAB@quad.stoffel.home>
On Mon, Feb 28, 2022 at 1:14 AM John Stoffel <john@quad.stoffel.home> wrote:
>
> On Sun, Feb 27, 2022 at 10:52:43PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > During a patch discussion, Linus brought up the option of changing
> > the C standard version from gnu89 to gnu99, which allows using variable
> > declaration inside of a for() loop. While the C99, C11 and later standards
> > introduce many other features, most of these are already available in
> > gnu89 as GNU extensions as well.
> >
> > An earlier attempt to do this when gcc-5 started defaulting to
> > -std=gnu11 failed because at the time that caused warnings about
> > designated initializers with older compilers. Now that gcc-5.1 is the
> > minimum compiler version used for building kernels, that is no longer a
> > concern. Similarly, the behavior of 'inline' functions changes between
> > gnu89 and gnu89, but this was taken care of by defining 'inline' to
>
> Typo here? Second one should be gnu99 right?
Fixed, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: john@quad.stoffel.home
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Michal Marek <michal.lkml@markovi.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Jonathan Corbet <corbet@lwn.net>,
linux-staging@lists.linux.dev,
Masahiro Yamada <masahiroy@kernel.org>,
llvm@lists.linux.dev, Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
greybus-dev@lists.linaro.org, Alex Shi <alexs@kernel.org>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Hu Haowen <src.res@email.cn>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-doc-tw-discuss@lists.sourceforge.net,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] Kbuild: remove -std=gnu89 from compiler arguments
Date: Mon, 28 Feb 2022 09:11:37 +0100 [thread overview]
Message-ID: <CAK8P3a1A8Y3F93FzbWum9U=_Mc8zR9T5p=tTkQK90ARan41EbA@mail.gmail.com> (raw)
In-Reply-To: <YhwT2Gw8vsQHPxAB@quad.stoffel.home>
On Mon, Feb 28, 2022 at 1:14 AM John Stoffel <john@quad.stoffel.home> wrote:
>
> On Sun, Feb 27, 2022 at 10:52:43PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > During a patch discussion, Linus brought up the option of changing
> > the C standard version from gnu89 to gnu99, which allows using variable
> > declaration inside of a for() loop. While the C99, C11 and later standards
> > introduce many other features, most of these are already available in
> > gnu89 as GNU extensions as well.
> >
> > An earlier attempt to do this when gcc-5 started defaulting to
> > -std=gnu11 failed because at the time that caused warnings about
> > designated initializers with older compilers. Now that gcc-5.1 is the
> > minimum compiler version used for building kernels, that is no longer a
> > concern. Similarly, the behavior of 'inline' functions changes between
> > gnu89 and gnu89, but this was taken care of by defining 'inline' to
>
> Typo here? Second one should be gnu99 right?
Fixed, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: john@quad.stoffel.home
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
llvm@lists.linux.dev, Jonathan Corbet <corbet@lwn.net>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Alex Shi <alexs@kernel.org>, Hu Haowen <src.res@email.cn>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-doc-tw-discuss@lists.sourceforge.net,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Kbuild: remove -std=gnu89 from compiler arguments
Date: Mon, 28 Feb 2022 09:11:37 +0100 [thread overview]
Message-ID: <CAK8P3a1A8Y3F93FzbWum9U=_Mc8zR9T5p=tTkQK90ARan41EbA@mail.gmail.com> (raw)
In-Reply-To: <YhwT2Gw8vsQHPxAB@quad.stoffel.home>
On Mon, Feb 28, 2022 at 1:14 AM John Stoffel <john@quad.stoffel.home> wrote:
>
> On Sun, Feb 27, 2022 at 10:52:43PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > During a patch discussion, Linus brought up the option of changing
> > the C standard version from gnu89 to gnu99, which allows using variable
> > declaration inside of a for() loop. While the C99, C11 and later standards
> > introduce many other features, most of these are already available in
> > gnu89 as GNU extensions as well.
> >
> > An earlier attempt to do this when gcc-5 started defaulting to
> > -std=gnu11 failed because at the time that caused warnings about
> > designated initializers with older compilers. Now that gcc-5.1 is the
> > minimum compiler version used for building kernels, that is no longer a
> > concern. Similarly, the behavior of 'inline' functions changes between
> > gnu89 and gnu89, but this was taken care of by defining 'inline' to
>
> Typo here? Second one should be gnu99 right?
Fixed, thanks!
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: john@quad.stoffel.home
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Michal Marek <michal.lkml@markovi.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Jonathan Corbet <corbet@lwn.net>,
linux-staging@lists.linux.dev,
Masahiro Yamada <masahiroy@kernel.org>,
llvm@lists.linux.dev, Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
greybus-dev@lists.linaro.org, Alex Shi <alexs@kernel.org>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Hu Haowen <src.res@email.cn>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-doc-tw-discuss@lists.sourceforge.net,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH] Kbuild: remove -std=gnu89 from compiler arguments
Date: Mon, 28 Feb 2022 09:11:37 +0100 [thread overview]
Message-ID: <CAK8P3a1A8Y3F93FzbWum9U=_Mc8zR9T5p=tTkQK90ARan41EbA@mail.gmail.com> (raw)
In-Reply-To: <YhwT2Gw8vsQHPxAB@quad.stoffel.home>
On Mon, Feb 28, 2022 at 1:14 AM John Stoffel <john@quad.stoffel.home> wrote:
>
> On Sun, Feb 27, 2022 at 10:52:43PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > During a patch discussion, Linus brought up the option of changing
> > the C standard version from gnu89 to gnu99, which allows using variable
> > declaration inside of a for() loop. While the C99, C11 and later standards
> > introduce many other features, most of these are already available in
> > gnu89 as GNU extensions as well.
> >
> > An earlier attempt to do this when gcc-5 started defaulting to
> > -std=gnu11 failed because at the time that caused warnings about
> > designated initializers with older compilers. Now that gcc-5.1 is the
> > minimum compiler version used for building kernels, that is no longer a
> > concern. Similarly, the behavior of 'inline' functions changes between
> > gnu89 and gnu89, but this was taken care of by defining 'inline' to
>
> Typo here? Second one should be gnu99 right?
Fixed, thanks!
Arnd
next prev parent reply other threads:[~2022-02-28 8:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 21:52 [PATCH] Kbuild: remove -std=gnu89 from compiler arguments Arnd Bergmann
2022-02-27 21:52 ` [Intel-gfx] " Arnd Bergmann
2022-02-27 21:52 ` Arnd Bergmann
2022-02-27 21:52 ` Arnd Bergmann
2022-02-27 22:36 ` Linus Torvalds
2022-02-27 22:36 ` [Intel-gfx] " Linus Torvalds
2022-02-27 22:36 ` Linus Torvalds
2022-02-27 22:36 ` Linus Torvalds
2022-02-28 8:07 ` Arnd Bergmann
2022-02-28 8:07 ` [Intel-gfx] " Arnd Bergmann
2022-02-28 8:07 ` Arnd Bergmann
2022-02-28 8:07 ` Arnd Bergmann
2022-02-27 23:04 ` [greybus-dev] " Alex Elder
2022-02-27 23:04 ` [Intel-gfx] " Alex Elder
2022-02-27 23:04 ` Alex Elder
2022-02-27 23:04 ` Alex Elder
2022-02-27 23:11 ` Linus Torvalds
2022-02-27 23:11 ` Linus Torvalds
2022-02-27 23:11 ` Linus Torvalds
2022-02-27 23:11 ` [Intel-gfx] " Linus Torvalds
2022-02-27 23:57 ` Alex Elder
2022-02-27 23:57 ` [Intel-gfx] " Alex Elder
2022-02-27 23:57 ` Alex Elder
2022-02-27 23:57 ` Alex Elder
2022-02-28 8:11 ` Arnd Bergmann
2022-02-28 8:11 ` [Intel-gfx] " Arnd Bergmann
2022-02-28 8:11 ` Arnd Bergmann
2022-02-28 8:11 ` Arnd Bergmann
2022-02-28 0:14 ` John Stoffel
2022-02-28 0:14 ` [Intel-gfx] " John Stoffel
2022-02-28 0:14 ` John Stoffel
2022-02-28 0:14 ` John Stoffel
2022-02-28 8:11 ` Arnd Bergmann [this message]
2022-02-28 8:11 ` [Intel-gfx] " Arnd Bergmann
2022-02-28 8:11 ` Arnd Bergmann
2022-02-28 8:11 ` Arnd Bergmann
2022-02-28 12:02 ` Christoph Hellwig
2022-02-28 12:02 ` Christoph Hellwig
2022-02-28 12:02 ` [Intel-gfx] " Christoph Hellwig
2022-02-28 21:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-02-28 21:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-01 6:20 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-02-28 17:36 [PATCH] " kernel test robot
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='CAK8P3a1A8Y3F93FzbWum9U=_Mc8zR9T5p=tTkQK90ARan41EbA@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=alexs@kernel.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=federico.vaga@vaga.pv.it \
--cc=greybus-dev@lists.linaro.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john@quad.stoffel.home \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc-tw-discuss@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=src.res@email.cn \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.