From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Daniel Cederman <cederman@gaisler.com>
Cc: gcc-patches@gcc.gnu.org, daniel@gaisler.com
Subject: Re: [PATCH 4/4] sparc: Add NOP in stack_protect_setsi if sparc_fix_b2bst enabled
Date: Wed, 15 Sep 2021 12:37:15 +0200 [thread overview]
Message-ID: <3064699.5fSG56mABF@fomalhaut> (raw)
In-Reply-To: <20210915093610.3112669-6-cederman@gaisler.com>
> gcc/ChangeLog:
>
> * config/sparc/sparc.md: Add NOP to prevent sensitive sequence for
> B2BST errata workaround.
OK everywhere, but the ChangeLog entry should be:
* config/sparc/sparc.md (stack_protect_set32): Add NOP...
Note that it's stack_protect_set32 on mainline and stack_protect_setsi before.
--
Eric Botcazou
next prev parent reply other threads:[~2021-09-15 10:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 9:36 [PATCH] sparc: Add scheduling information for LEON5 Daniel Cederman
2021-09-15 9:36 ` [PATCH] sparc: Print out bit names for LEON and LEON3 with -mdebug Daniel Cederman
2021-09-15 10:19 ` Eric Botcazou
2021-09-15 9:36 ` [PATCH 1/4] sparc: Treat more instructions as load or store in errata workarounds Daniel Cederman
2021-09-15 10:23 ` Eric Botcazou
2021-09-15 9:36 ` [PATCH 2/4] sparc: Skip all empty assembly statements Daniel Cederman
2021-09-15 10:31 ` Eric Botcazou
2021-09-15 9:36 ` [PATCH 3/4] sparc: Prevent atomic instructions in beginning of functions for UT700 Daniel Cederman
2021-09-15 10:32 ` Eric Botcazou
2021-09-15 9:36 ` [PATCH 4/4] sparc: Add NOP in stack_protect_setsi if sparc_fix_b2bst enabled Daniel Cederman
2021-09-15 10:37 ` Eric Botcazou [this message]
2021-09-15 10:18 ` [PATCH] sparc: Add scheduling information for LEON5 Eric Botcazou
2021-09-15 11:04 ` Daniel Cederman
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=3064699.5fSG56mABF@fomalhaut \
--to=ebotcazou@libertysurf.fr \
--cc=cederman@gaisler.com \
--cc=daniel@gaisler.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).