All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Joe Perches <joe@perches.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	linux-riscv@lists.infradead.org,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Will Deacon <will@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Sun, 2 May 2021 14:08:31 -0700	[thread overview]
Message-ID: <CAHk-=wjGJskk5EwnDCccs6DcLytE2yx76+P_W-n1-B5zq0M3KA@mail.gmail.com> (raw)
In-Reply-To: <20210502203253.GH10366@gate.crashing.org>

On Sun, May 2, 2021 at 1:38 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> The point is, you inconvenience users if you require a compiler version
> they do not already have.  Five years might be fine, but three years is
> not.

So this should be our main issue - not how old a compiler is, but how
our compiler version limitations end up possibly making it harder for
users to upgrade.

Of course, one issue there is whether said users would have upgraded
regardless - if you have a very old distribution, how likely are you
to upgrade the kernel at all?

But we do very much want to encourage people to upgrade their kernels,
even if they might be running otherwise fairly old user space. If for
no other reason than that it's good for our kernel coverage testing -
the more different distributions people test a new kernel with, the
better. And some of the less common architectures have their own
issues, with distros possibly not even supporting them any more (if
they ever did - considering all the odd ad-hoc cross-compiler builds
people have had..)

This is why "our clang support requires a very recent version of
clang" is not relevant - distributions won't have old versions of
clang anyway, and even if they do, such distributions will be
gcc-based, so "build the kernel with clang" for that situation is
perhaps an exercise for some intrepid person who is willing to do odd
and unusual things, and might as well build their own clang version
too.

So I really wish people didn't get hung about some "three years ago"
or similar. It's not relevant.

What is relevant is what version of gcc various distributions actually
have reasonably easily available, and how old and relevant the
distributions are. We did decide that (just as an example) RHEL 7 was
too old to worry about when we updated the gcc version requirement
last time.

Last year, Arnd and Kirill (maybe others were involved too) made a
list of distros and older gcc versions. But I don't think anybody
actually _maintains_ such a list. It would be perhaps interesting to
have some way to check what compiler versions are being offered by
different distros.

           Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Joe Perches <joe@perches.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	 Masahiro Yamada <masahiroy@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>,  Arnd Bergmann <arnd@arndb.de>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	 Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	 Paul Mackerras <paulus@samba.org>,
	linux-riscv@lists.infradead.org,
	 linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Will Deacon <will@kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Sun, 2 May 2021 14:08:31 -0700	[thread overview]
Message-ID: <CAHk-=wjGJskk5EwnDCccs6DcLytE2yx76+P_W-n1-B5zq0M3KA@mail.gmail.com> (raw)
In-Reply-To: <20210502203253.GH10366@gate.crashing.org>

On Sun, May 2, 2021 at 1:38 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> The point is, you inconvenience users if you require a compiler version
> they do not already have.  Five years might be fine, but three years is
> not.

So this should be our main issue - not how old a compiler is, but how
our compiler version limitations end up possibly making it harder for
users to upgrade.

Of course, one issue there is whether said users would have upgraded
regardless - if you have a very old distribution, how likely are you
to upgrade the kernel at all?

But we do very much want to encourage people to upgrade their kernels,
even if they might be running otherwise fairly old user space. If for
no other reason than that it's good for our kernel coverage testing -
the more different distributions people test a new kernel with, the
better. And some of the less common architectures have their own
issues, with distros possibly not even supporting them any more (if
they ever did - considering all the odd ad-hoc cross-compiler builds
people have had..)

This is why "our clang support requires a very recent version of
clang" is not relevant - distributions won't have old versions of
clang anyway, and even if they do, such distributions will be
gcc-based, so "build the kernel with clang" for that situation is
perhaps an exercise for some intrepid person who is willing to do odd
and unusual things, and might as well build their own clang version
too.

So I really wish people didn't get hung about some "three years ago"
or similar. It's not relevant.

What is relevant is what version of gcc various distributions actually
have reasonably easily available, and how old and relevant the
distributions are. We did decide that (just as an example) RHEL 7 was
too old to worry about when we updated the gcc version requirement
last time.

Last year, Arnd and Kirill (maybe others were involved too) made a
list of distros and older gcc versions. But I don't think anybody
actually _maintains_ such a list. It would be perhaps interesting to
have some way to check what compiler versions are being offered by
different distros.

           Linus

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Will Deacon <will@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Joe Perches <joe@perches.com>, Paul Mackerras <paulus@samba.org>,
	linux-riscv@lists.infradead.org, Miguel Ojeda <ojeda@kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Sun, 2 May 2021 14:08:31 -0700	[thread overview]
Message-ID: <CAHk-=wjGJskk5EwnDCccs6DcLytE2yx76+P_W-n1-B5zq0M3KA@mail.gmail.com> (raw)
In-Reply-To: <20210502203253.GH10366@gate.crashing.org>

On Sun, May 2, 2021 at 1:38 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> The point is, you inconvenience users if you require a compiler version
> they do not already have.  Five years might be fine, but three years is
> not.

So this should be our main issue - not how old a compiler is, but how
our compiler version limitations end up possibly making it harder for
users to upgrade.

Of course, one issue there is whether said users would have upgraded
regardless - if you have a very old distribution, how likely are you
to upgrade the kernel at all?

But we do very much want to encourage people to upgrade their kernels,
even if they might be running otherwise fairly old user space. If for
no other reason than that it's good for our kernel coverage testing -
the more different distributions people test a new kernel with, the
better. And some of the less common architectures have their own
issues, with distros possibly not even supporting them any more (if
they ever did - considering all the odd ad-hoc cross-compiler builds
people have had..)

This is why "our clang support requires a very recent version of
clang" is not relevant - distributions won't have old versions of
clang anyway, and even if they do, such distributions will be
gcc-based, so "build the kernel with clang" for that situation is
perhaps an exercise for some intrepid person who is willing to do odd
and unusual things, and might as well build their own clang version
too.

So I really wish people didn't get hung about some "three years ago"
or similar. It's not relevant.

What is relevant is what version of gcc various distributions actually
have reasonably easily available, and how old and relevant the
distributions are. We did decide that (just as an example) RHEL 7 was
too old to worry about when we updated the gcc version requirement
last time.

Last year, Arnd and Kirill (maybe others were involved too) made a
list of distros and older gcc versions. But I don't think anybody
actually _maintains_ such a list. It would be perhaps interesting to
have some way to check what compiler versions are being offered by
different distros.

           Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Joe Perches <joe@perches.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	 Masahiro Yamada <masahiroy@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>,  Arnd Bergmann <arnd@arndb.de>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	 Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	 Paul Mackerras <paulus@samba.org>,
	linux-riscv@lists.infradead.org,
	 linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Will Deacon <will@kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Sun, 2 May 2021 14:08:31 -0700	[thread overview]
Message-ID: <CAHk-=wjGJskk5EwnDCccs6DcLytE2yx76+P_W-n1-B5zq0M3KA@mail.gmail.com> (raw)
In-Reply-To: <20210502203253.GH10366@gate.crashing.org>

On Sun, May 2, 2021 at 1:38 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> The point is, you inconvenience users if you require a compiler version
> they do not already have.  Five years might be fine, but three years is
> not.

So this should be our main issue - not how old a compiler is, but how
our compiler version limitations end up possibly making it harder for
users to upgrade.

Of course, one issue there is whether said users would have upgraded
regardless - if you have a very old distribution, how likely are you
to upgrade the kernel at all?

But we do very much want to encourage people to upgrade their kernels,
even if they might be running otherwise fairly old user space. If for
no other reason than that it's good for our kernel coverage testing -
the more different distributions people test a new kernel with, the
better. And some of the less common architectures have their own
issues, with distros possibly not even supporting them any more (if
they ever did - considering all the odd ad-hoc cross-compiler builds
people have had..)

This is why "our clang support requires a very recent version of
clang" is not relevant - distributions won't have old versions of
clang anyway, and even if they do, such distributions will be
gcc-based, so "build the kernel with clang" for that situation is
perhaps an exercise for some intrepid person who is willing to do odd
and unusual things, and might as well build their own clang version
too.

So I really wish people didn't get hung about some "three years ago"
or similar. It's not relevant.

What is relevant is what version of gcc various distributions actually
have reasonably easily available, and how old and relevant the
distributions are. We did decide that (just as an example) RHEL 7 was
too old to worry about when we updated the gcc version requirement
last time.

Last year, Arnd and Kirill (maybe others were involved too) made a
list of distros and older gcc versions. But I don't think anybody
actually _maintains_ such a list. It would be perhaps interesting to
have some way to check what compiler versions are being offered by
different distros.

           Linus

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-05-02 21:08 UTC|newest]

Thread overview: 146+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 15:15 [PATCH] Raise the minimum GCC version to 5.2 Masahiro Yamada
2021-05-01 15:15 ` Masahiro Yamada
2021-05-01 15:15 ` Masahiro Yamada
2021-05-01 15:15 ` Masahiro Yamada
2021-05-01 15:52 ` Miguel Ojeda
2021-05-01 15:52   ` Miguel Ojeda
2021-05-01 15:52   ` Miguel Ojeda
2021-05-01 15:52   ` Miguel Ojeda
2021-05-01 17:38   ` Christophe Leroy
2021-05-01 17:38     ` Christophe Leroy
2021-05-01 17:38     ` Christophe Leroy
2021-05-01 17:38     ` Christophe Leroy
2021-05-02  2:41   ` Joe Perches
2021-05-02  2:41     ` Joe Perches
2021-05-02  2:41     ` Joe Perches
2021-05-02  2:41     ` Joe Perches
2021-05-02 18:30     ` Segher Boessenkool
2021-05-02 18:30       ` Segher Boessenkool
2021-05-02 18:30       ` Segher Boessenkool
2021-05-02 18:30       ` Segher Boessenkool
2021-05-02 20:00       ` Joe Perches
2021-05-02 20:00         ` Joe Perches
2021-05-02 20:00         ` Joe Perches
2021-05-02 20:00         ` Joe Perches
2021-05-02 20:32         ` Segher Boessenkool
2021-05-02 20:32           ` Segher Boessenkool
2021-05-02 20:32           ` Segher Boessenkool
2021-05-02 20:32           ` Segher Boessenkool
2021-05-02 21:05           ` Ali Kaasinen
2021-05-02 21:05             ` Ali Kaasinen
2021-05-02 21:05             ` Ali Kaasinen
2021-05-02 21:05             ` Ali Kaasinen
2021-05-02 21:08           ` Linus Torvalds [this message]
2021-05-02 21:08             ` Linus Torvalds
2021-05-02 21:08             ` Linus Torvalds
2021-05-02 21:08             ` Linus Torvalds
2021-05-02 22:30             ` Matthew Wilcox
2021-05-02 22:30               ` Matthew Wilcox
2021-05-02 22:30               ` Matthew Wilcox
2021-05-02 22:30               ` Matthew Wilcox
2021-05-03  7:34               ` Alexander Dahl
2021-05-03  7:34                 ` Alexander Dahl
2021-05-03  7:34                 ` Alexander Dahl
2021-05-03  7:34                 ` Alexander Dahl
2021-05-03  8:54                 ` Joe Perches
2021-05-03  8:54                   ` Joe Perches
2021-05-03  8:54                   ` Joe Perches
2021-05-03  8:54                   ` Joe Perches
2021-05-03  9:25                 ` Arnd Bergmann
2021-05-03  9:25                   ` Arnd Bergmann
2021-05-03  9:25                   ` Arnd Bergmann
2021-05-03  9:25                   ` Arnd Bergmann
2021-05-03 12:20                   ` David Laight
2021-05-03 12:20                     ` David Laight
2021-05-03 12:20                     ` David Laight
2021-05-03 13:10                     ` Miguel Ojeda
2021-05-03 13:10                       ` Miguel Ojeda
2021-05-03 13:10                       ` Miguel Ojeda
2021-05-03 13:10                       ` Miguel Ojeda
2021-05-04  5:30                   ` Alexander Dahl
2021-05-04  5:30                     ` Alexander Dahl
2021-05-04  5:30                     ` Alexander Dahl
2021-05-04  5:30                     ` Alexander Dahl
2021-05-04  6:33                     ` Christophe Leroy
2021-05-04  6:33                       ` Christophe Leroy
2021-05-04  6:33                       ` Christophe Leroy
2021-05-04 12:07                     ` Arnd Bergmann
2021-05-04 12:07                       ` Arnd Bergmann
2021-05-04 12:07                       ` Arnd Bergmann
2021-05-04 12:07                       ` Arnd Bergmann
2021-05-04 13:25                   ` Andy Shevchenko
2021-05-04 13:25                     ` Andy Shevchenko
2021-05-04 13:25                     ` Andy Shevchenko
2021-05-04 13:25                     ` Andy Shevchenko
2021-05-03 11:35               ` Arnd Bergmann
2021-05-03 11:35                 ` Arnd Bergmann
2021-05-03 11:35                 ` Arnd Bergmann
2021-05-03 11:35                 ` Arnd Bergmann
2021-05-03  9:49             ` Kirill A. Shutemov
2021-05-03  9:49               ` Kirill A. Shutemov
2021-05-03  9:49               ` Kirill A. Shutemov
2021-05-03  9:49               ` Kirill A. Shutemov
2021-05-02 21:23           ` Joe Perches
2021-05-02 21:23             ` Joe Perches
2021-05-02 21:23             ` Joe Perches
2021-05-02 21:23             ` Joe Perches
2021-05-03  0:44             ` Segher Boessenkool
2021-05-03  0:44               ` Segher Boessenkool
2021-05-03  0:44               ` Segher Boessenkool
2021-05-03  0:44               ` Segher Boessenkool
2021-05-03  9:57               ` Arnd Bergmann
2021-05-03  9:57                 ` Arnd Bergmann
2021-05-03  9:57                 ` Arnd Bergmann
2021-05-03  9:57                 ` Arnd Bergmann
2021-05-04  7:56     ` Ben Dooks
2021-05-04  7:56       ` Ben Dooks
2021-05-04  7:56       ` Ben Dooks
2021-05-04  7:56       ` Ben Dooks
2021-05-04  8:38       ` Miguel Ojeda
2021-05-04  8:38         ` Miguel Ojeda
2021-05-04  8:38         ` Miguel Ojeda
2021-05-04  8:38         ` Miguel Ojeda
2021-05-04  9:22         ` Michal Suchánek
2021-05-04  9:22           ` Michal Suchánek
2021-05-04  9:22           ` Michal Suchánek
2021-05-04  9:22           ` Michal Suchánek
2021-05-04 12:09           ` Miguel Ojeda
2021-05-04 12:09             ` Miguel Ojeda
2021-05-04 12:09             ` Miguel Ojeda
2021-05-04 12:09             ` Miguel Ojeda
2021-05-04 12:17             ` Michal Suchánek
2021-05-04 12:17               ` Michal Suchánek
2021-05-04 12:17               ` Michal Suchánek
2021-05-04 12:17               ` Michal Suchánek
2021-05-04 12:26               ` Christophe Leroy
2021-05-04 12:26                 ` Christophe Leroy
2021-05-04 12:26                 ` Christophe Leroy
2021-05-04 12:26                 ` Christophe Leroy
2021-05-02 18:37 ` Segher Boessenkool
2021-05-02 18:37   ` Segher Boessenkool
2021-05-02 18:37   ` Segher Boessenkool
2021-05-02 18:37   ` Segher Boessenkool
2021-05-03  6:16 ` Christophe Leroy
2021-05-03  6:16   ` Christophe Leroy
2021-05-03  6:16   ` Christophe Leroy
2021-05-03  6:16   ` Christophe Leroy
2021-05-04  2:13   ` Masahiro Yamada
2021-05-04  2:13     ` Masahiro Yamada
2021-05-04  2:13     ` Masahiro Yamada
2021-05-04  2:13     ` Masahiro Yamada
2021-05-04 13:18   ` Andy Shevchenko
2021-05-04 13:18     ` Andy Shevchenko
2021-05-04 13:18     ` Andy Shevchenko
2021-05-04 13:18     ` Andy Shevchenko
2021-05-03 12:27 ` David Sterba
2021-05-03 12:27   ` David Sterba
2021-05-03 12:27   ` David Sterba
2021-05-03 12:27   ` David Sterba
2021-05-15  7:14 ` Pavel Machek
2021-05-15  7:14   ` Pavel Machek
2021-05-15  7:14   ` Pavel Machek
2021-05-15  7:14   ` Pavel Machek
2021-05-15  7:27   ` Joe Perches
2021-05-15  7:27     ` Joe Perches
2021-05-15  7:27     ` Joe Perches
2021-05-15  7:27     ` Joe Perches

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='CAHk-=wjGJskk5EwnDCccs6DcLytE2yx76+P_W-n1-B5zq0M3KA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=masahiroy@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulus@samba.org \
    --cc=segher@kernel.crashing.org \
    --cc=will@kernel.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.