public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: H.J. Lu <hjl@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r10-10228] x86: Document -fcf-protection requires i686 or newer Date: Thu, 21 Oct 2021 19:11:26 +0000 (GMT) [thread overview] Message-ID: <20211021191126.0C3223858416@sourceware.org> (raw) https://gcc.gnu.org/g:523dc71f5cb858da18e1f648269746dab519b445 commit r10-10228-g523dc71f5cb858da18e1f648269746dab519b445 Author: H.J. Lu <hjl.tools@gmail.com> Date: Thu Oct 21 09:45:14 2021 -0700 x86: Document -fcf-protection requires i686 or newer PR target/98667 * doc/invoke.texi: Document -fcf-protection requires i686 or new. (cherry picked from commit 1373066a46d8d47abd97e46a005aef3b3dbfe94a) Diff: --- gcc/doc/invoke.texi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index f2377279a63..6d3cfcc664e 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -13886,7 +13886,8 @@ which functions and calls should be skipped from instrumentation (@pxref{Function Attributes}). Currently the x86 GNU/Linux target provides an implementation based -on Intel Control-flow Enforcement Technology (CET). +on Intel Control-flow Enforcement Technology (CET) which works for +i686 processor or newer. @item -fstack-protector @opindex fstack-protector
reply other threads:[~2021-10-21 19:11 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=20211021191126.0C3223858416@sourceware.org \ --to=hjl@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).