public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: SRINATH PARVATHANENI <sripar01@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5306] arm: Documentation fix for -mbranch-protection option. Date: Mon, 23 Jan 2023 13:38:04 +0000 (GMT) [thread overview] Message-ID: <20230123133804.C877E3858D32@sourceware.org> (raw) https://gcc.gnu.org/g:b457cab64038cd9b7a8481594ff673f1822681f6 commit r13-5306-gb457cab64038cd9b7a8481594ff673f1822681f6 Author: Srinath Parvathaneni <srinath.parvathaneni@arm.com> Date: Mon Jan 23 13:37:07 2023 +0000 arm: Documentation fix for -mbranch-protection option. This patch fixes the documentation for -mbranch-protection command line option. gcc/ChangeLog: 2023-01-23 Srinath Parvathaneni <srinath.parvathaneni@arm.com> * doc/invoke.texi (-mbranch-protection): Update documentation. Diff: --- gcc/doc/invoke.texi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index f1c0b52012b..06d77983e30 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -22564,8 +22564,7 @@ The opposite @option{-mno-fdpic} option is useful (and required) to build the Linux kernel using the same (@code{arm-*-uclinuxfdpiceabi}) toolchain as the one used to build the userland programs. -@item --mbranch-protection=@var{none}|@var{standard}|@var{pac-ret}[+@var{leaf}][+@var{bti}]|@var{bti}[+@var{pac-ret}[+@var{leaf}]] +@item -mbranch-protection=@var{none}|@var{standard}|@var{pac-ret}[+@var{leaf}][+@var{bti}]|@var{bti}[+@var{pac-ret}[+@var{leaf}]] @opindex mbranch-protection Enable branch protection features (armv8.1-m.main only). @samp{none} generate code without branch protection or return address
reply other threads:[~2023-01-23 13:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230123133804.C877E3858D32@sourceware.org \ --to=sripar01@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).