public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113039] [14 Regression] -fcf-protection -fcf-protection=branch doesn't work Date: Fri, 12 Jan 2024 03:18:41 +0000 [thread overview] Message-ID: <bug-113039-4-i0RKO0ksFN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113039-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113039 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:75ed46558a2e085ba12641a47112e37f114faee0 commit r14-7164-g75ed46558a2e085ba12641a47112e37f114faee0 Author: liuhongt <hongtao.liu@intel.com> Date: Mon Jan 8 14:04:38 2024 +0800 Update documents for fcf-protection= After r14-2692-g1c6231c05bdcca, the option is defined as EnumSet and -fcf-protection=branch won't unset any others bits since they're in different groups. So to override -fcf-protection, an explicit -fcf-protection=none needs to be added and then with -fcf-protection=XXX gcc/ChangeLog: PR target/113039 * doc/invoke.texi (fcf-protection=): Update documents.
next prev parent reply other threads:[~2024-01-12 3:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-16 2:04 [Bug target/113039] New: " hjl.tools at gmail dot com 2023-12-16 2:14 ` [Bug target/113039] " hjl.tools at gmail dot com 2023-12-16 2:23 ` hjl.tools at gmail dot com 2023-12-18 2:42 ` liuhongt at gcc dot gnu.org 2023-12-18 8:08 ` rguenth at gcc dot gnu.org 2024-01-12 3:18 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-12 3:21 ` liuhongt at gcc dot gnu.org
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=bug-113039-4-i0RKO0ksFN@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).