All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian Cain" <bcain@codeaurora.org>
To: 'Nick Desaulniers' <ndesaulniers@google.com>,
	'Guenter Roeck' <linux@roeck-us.net>
Cc: 'Will Deacon' <will@kernel.org>,
	linux-hexagon@vger.kernel.org,
	'LKML' <linux-kernel@vger.kernel.org>,
	'Thomas Gleixner' <tglx@linutronix.de>,
	'Masahiro Yamada' <masahiroy@kernel.org>,
	'Peter Zijlstra' <peterz@infradead.org>,
	'Arnd Bergmann' <arnd@arndb.de>,
	sidneym@codeaurora.org
Subject: RE: [PATCH] compiler/gcc: Raise minimum GCC version for kernel builds to 4.8
Date: Tue, 26 May 2020 16:57:07 -0500	[thread overview]
Message-ID: <04ca01d633a8$9abb8070$d0328150$@codeaurora.org> (raw)
In-Reply-To: <CAKwvOdnrsCCt_HU+fows6kBCs2jGcikDtMm_otQSKFEgqfojJw@mail.gmail.com>

> -----Original Message-----
> From: linux-hexagon-owner@vger.kernel.org <linux-hexagon-
> owner@vger.kernel.org> On Behalf Of Nick Desaulniers
...
> On Tue, May 26, 2020 at 8:30 AM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > On Mon, May 11, 2020 at 09:41:37PM +0100, Will Deacon wrote:
> > > It is very rare to see versions of GCC prior to 4.8 being used to
> > > build the mainline kernel. These old compilers are also known to
> > > have codegen issues which can lead to silent miscompilation:
> > >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145
> > >
> > > Raise the minimum GCC version to 4.8 for building the kernel and
> > > remove some tautological Kconfig dependencies as a consequence.
> >
> > My hexagon compiler is v4.6.1, and I have been unable to find a more
> > recent version. Does anyone happen to have a pointer to a hexagon
> > toolchain with gcc 4.8 or later ?
> 
> IIUC, hexagon moved to LLVM, though that target still has issues building the
> kernel.
> https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+lab
> el%3A%22%5BARCH%5D+hexagon%22

Indeed, we did move to llvm.  The build works with the clang_rt-builtins lib.  But that issue indicates that it's an unnecessary wart to require that.  From what I understand, other arches contribute these builtins content to the kernel build, so we'll do the same.

I'll prioritize this update.

-Brian


WARNING: multiple messages have this Message-ID (diff)
From: "Brian Cain" <bcain@codeaurora.org>
To: "'Nick Desaulniers'" <ndesaulniers@google.com>,
	"'Guenter Roeck'" <linux@roeck-us.net>
Cc: "'Will Deacon'" <will@kernel.org>,
	<linux-hexagon@vger.kernel.org>,
	"'LKML'" <linux-kernel@vger.kernel.org>,
	"'Thomas Gleixner'" <tglx@linutronix.de>,
	"'Masahiro Yamada'" <masahiroy@kernel.org>,
	"'Peter Zijlstra'" <peterz@infradead.org>,
	"'Arnd Bergmann'" <arnd@arndb.de>, <sidneym@codeaurora.org>
Subject: RE: [PATCH] compiler/gcc: Raise minimum GCC version for kernel builds to 4.8
Date: Tue, 26 May 2020 16:57:07 -0500	[thread overview]
Message-ID: <04ca01d633a8$9abb8070$d0328150$@codeaurora.org> (raw)
In-Reply-To: <CAKwvOdnrsCCt_HU+fows6kBCs2jGcikDtMm_otQSKFEgqfojJw@mail.gmail.com>

> -----Original Message-----
> From: linux-hexagon-owner@vger.kernel.org <linux-hexagon-
> owner@vger.kernel.org> On Behalf Of Nick Desaulniers
...
> On Tue, May 26, 2020 at 8:30 AM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > On Mon, May 11, 2020 at 09:41:37PM +0100, Will Deacon wrote:
> > > It is very rare to see versions of GCC prior to 4.8 being used to
> > > build the mainline kernel. These old compilers are also known to
> > > have codegen issues which can lead to silent miscompilation:
> > >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145
> > >
> > > Raise the minimum GCC version to 4.8 for building the kernel and
> > > remove some tautological Kconfig dependencies as a consequence.
> >
> > My hexagon compiler is v4.6.1, and I have been unable to find a more
> > recent version. Does anyone happen to have a pointer to a hexagon
> > toolchain with gcc 4.8 or later ?
> 
> IIUC, hexagon moved to LLVM, though that target still has issues building the
> kernel.
> https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+lab
> el%3A%22%5BARCH%5D+hexagon%22

Indeed, we did move to llvm.  The build works with the clang_rt-builtins lib.  But that issue indicates that it's an unnecessary wart to require that.  From what I understand, other arches contribute these builtins content to the kernel build, so we'll do the same.

I'll prioritize this update.

-Brian


  parent reply	other threads:[~2020-05-26 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 15:30 [PATCH] compiler/gcc: Raise minimum GCC version for kernel builds to 4.8 Guenter Roeck
2020-05-26 15:40 ` Nick Desaulniers
2020-05-26 16:03   ` Guenter Roeck
2020-05-26 16:08     ` Nick Desaulniers
2020-05-26 21:57   ` Brian Cain [this message]
2020-05-26 21:57     ` Brian Cain

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='04ca01d633a8$9abb8070$d0328150$@codeaurora.org' \
    --to=bcain@codeaurora.org \
    --cc=arnd@arndb.de \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    --cc=sidneym@codeaurora.org \
    --cc=tglx@linutronix.de \
    --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.