public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/89701] Provide -fcf-protection=branch,return
Date: Tue, 12 Jan 2021 09:04:18 +0000 [thread overview]
Message-ID: <bug-89701-4-fb4sZrgngo@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 #2 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Marek Polacek from comment #1)
> Confirmed. While we support -fcf-protection=branch and
> -fcf-protection=return,
> -fcf-protection=branch,return gives an error:
>
> xgcc: error: unknown Control-Flow Protection Level ‘branch,return’
> xgcc: note: valid arguments to ‘-fcf-protection=’ are: branch check full
> none retur
We can add a new EnumValue with string (branch,return) and value ({(enum
cf_protection_level) (CF_BRANCH | CF_RETURN)}) for this specific case, but the
implementation is too cumbersome considering the many permutations possible.
Another way is adding parser_cf_protection_options, called in
parse_sanitizer_options, decoding the string value and set corresponding bit in
flag_cf_protection.
next prev parent reply other threads:[~2021-01-12 9:04 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 ` mpolacek at gcc dot gnu.org
2021-01-12 9:04 ` crazylht at gmail dot com [this message]
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
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-fb4sZrgngo@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: 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).