mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Will Deacon <will@kernel.org>, Brian Cain <bcain@codeaurora.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>
Subject: Re: [PATCH] compiler/gcc: Raise minimum GCC version for kernel builds to 4.8
Date: Tue, 26 May 2020 09:03:55 -0700	[thread overview]
Message-ID: <8c5f8a2c-0ca2-b2f2-4278-d02198d4dd8d@roeck-us.net> (raw)
In-Reply-To: <CAKwvOdnrsCCt_HU+fows6kBCs2jGcikDtMm_otQSKFEgqfojJw@mail.gmail.com>

Hi Nick,

On 5/26/20 8:40 AM, Nick Desaulniers wrote:
> 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+label%3A%22%5BARCH%5D+hexagon%22
> 

That won't help me for my build tests. It is bad enough having to maintain
one compiler. I don't want to add another one to the mix, and I'll happily
leave llvm build tests for ClangBuiltLinux. Guess I'll have to stop hexagon
test builds starting with 5.8.

Guenter

  reply	other threads:[~2020-05-26 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 15:30 Guenter Roeck
2020-05-26 15:40 ` Nick Desaulniers
2020-05-26 16:03   ` Guenter Roeck [this message]
2020-05-26 16:08     ` Nick Desaulniers
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=8c5f8a2c-0ca2-b2f2-4278-d02198d4dd8d@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=arnd@arndb.de \
    --cc=bcain@codeaurora.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®