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/89701] Provide -fcf-protection=branch,return Date: Fri, 21 Jul 2023 03:07:13 +0000 [thread overview] Message-ID: <bug-89701-4-QYyLbYMuYT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89701-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89701 --- Comment #5 from CVS 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:1c6231c05bdccab3a21abcbb75e2094ea3e98782 commit r14-2692-g1c6231c05bdccab3a21abcbb75e2094ea3e98782 Author: liuhongt <hongtao.liu@intel.com> Date: Fri May 12 15:15:08 2023 +0800 Provide -fcf-protection=branch,return. Use EnumSet instead of EnumBitSet since CF_FULL is not power of 2. It is a bit tricky for sets classification, cf_branch and cf_return should be in different sets, but they both "conflicts" cf_full, cf_none. And current EnumSet don't handle this well. So in the current implementation, only cf_full,cf_none are exclusive to each other, but they can be combined with any cf_branch, cf_return, cf_check. It's not perfect, but still an improvement than original one. gcc/ChangeLog: PR target/89701 * common.opt: (fcf-protection=): Add EnumSet attribute to support combination of params. gcc/testsuite/ChangeLog: * c-c++-common/fcf-protection-10.c: New test. * c-c++-common/fcf-protection-11.c: New test. * c-c++-common/fcf-protection-12.c: New test. * c-c++-common/fcf-protection-8.c: New test. * c-c++-common/fcf-protection-9.c: New test. * gcc.target/i386/pr89701-1.c: New test. * gcc.target/i386/pr89701-2.c: New test. * gcc.target/i386/pr89701-3.c: New test.
next prev parent reply other threads:[~2023-07-21 3:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89701-4@http.gcc.gnu.org/bugzilla/> 2021-01-11 20:30 ` [Bug other/89701] " mpolacek at gcc dot gnu.org 2021-01-12 9:04 ` crazylht at gmail dot com 2021-01-12 9:53 ` crazylht at gmail dot com 2021-01-26 6:36 ` [Bug target/89701] " crazylht at gmail dot com 2021-05-04 12:32 ` rguenth at gcc dot gnu.org 2023-07-21 3:07 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-21 3:10 ` crazylht at gmail dot com
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-89701-4-QYyLbYMuYT@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).