All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: kconfig: Update and comment GCC version check for kernel BTI
Date: Tue, 12 May 2020 13:00:59 +0100	[thread overview]
Message-ID: <20200512120059.GF5110@sirena.org.uk> (raw)
In-Reply-To: <20200512115458.4985-1-will@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 661 bytes --]

On Tue, May 12, 2020 at 12:54:58PM +0100, Will Deacon wrote:
> Some versions of GCC are known to suffer from a BTI code generation bug,
> meaning that CONFIG_CC_HAS_BRANCH_PROT_PAC_RET_BTI cannot be solely used
> to determine whether or not we can compile with kernel with BTI enabled.
> 
> Update the BTI Kconfig entry to refer to the relevant GCC bugzilla entry
> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94697) and update the check
> now that the fix has been merged into GCC release 10.1.

Acked-by: Mark Brown <broonie@kernel.org>

There wasn't a GCC 10.0 release, I was a little surprised at the
numbering of the initial GCC 10 release.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

      reply	other threads:[~2020-05-12 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 11:54 [PATCH] arm64: kconfig: Update and comment GCC version check for kernel BTI Will Deacon
2020-05-12 12:00 ` Mark Brown [this message]

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=20200512120059.GF5110@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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.