From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <ross@burtonini.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] gcc: enable branch protection by standard
Date: Fri, 21 May 2021 06:12:27 +0000 [thread overview]
Message-ID: <YKdPSn9E1MOUmJsz@korppu> (raw)
In-Reply-To: <20210520171511.3177430-1-ross.burton@arm.com>
Hi,
On Thu, May 20, 2021 at 06:15:11PM +0100, Ross Burton wrote:
> Pass --enable-standard-branch-protection. This is an aarch64-specific
> option (currently) which does nothing on other targets. On aarch64 this
> generates code uses BTI/PAC instructions to mitigate Return Orientated
> Programming attacks. This approach is backwards compatible and the code
> size/performance impact is typically negliable.
>
> More details can be found at
> https://events.static.linuxfound.org/sites/events/files/slides/slides_23.pdf
Do you recommend this for dunfell and other stable releases? Any requirements
to gcc version? What about clang?
Cheers,
-Mikko
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
> meta/recipes-devtools/gcc/gcc-configure-common.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> index a64c4caf00..dc7f458b25 100644
> --- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
> +++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> @@ -40,6 +40,7 @@ EXTRA_OECONF = "\
> ${@get_gcc_mips_plt_setting(bb, d)} \
> ${@get_gcc_ppc_plt_settings(bb, d)} \
> ${@get_gcc_multiarch_setting(bb, d)} \
> + --enable-standard-branch-protection \
> "
>
> # glibc version is a minimum controlling whether features are enabled.
> --
> 2.25.1
>
>
>
>
next prev parent reply other threads:[~2021-05-21 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 17:15 [PATCH] gcc: enable branch protection by standard Ross Burton
2021-05-20 18:12 ` [OE-core] " Khem Raj
2021-05-21 6:12 ` Mikko Rapeli [this message]
2021-05-21 7:33 ` Khem Raj
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=YKdPSn9E1MOUmJsz@korppu \
--to=mikko.rapeli@bmw.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.com \
/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