public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug driver/114606] New: -Whardened doesn't trigger with -fcf-protection=none
@ 2024-04-05 16:09 mpolacek at gcc dot gnu.org
  2024-04-05 16:09 ` [Bug driver/114606] " mpolacek at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2024-04-05 16:09 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114606

            Bug ID: 114606
           Summary: -Whardened doesn't trigger with -fcf-protection=none
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mpolacek at gcc dot gnu.org
  Target Milestone: ---

-Whardened warns when -fhardened couldn't enable a hardening option because
that option was disabled on the command line, e.g.:

$ ./cc1plus -quiet g.C  -fhardened -O2 -fstack-protector
cc1plus: warning: ‘-fstack-protector-strong’ is not enabled by ‘-fhardened’
because it was specified on the command line [-Whardened]

but it doesn't work as expected with -fcf-protection=none:

$ ./cc1plus -quiet g.C  -fhardened -O2 -fcf-protection=none
# should warn

because we're checking == CF_NONE which doesn't distinguish between nothing and
-fcf-protection=none.  I'm hoping the fix is simply to use OPTION_SET_P.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-04-10 21:28 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-05 16:09 [Bug driver/114606] New: -Whardened doesn't trigger with -fcf-protection=none mpolacek at gcc dot gnu.org
2024-04-05 16:09 ` [Bug driver/114606] " mpolacek at gcc dot gnu.org
2024-04-10 21:28 ` [Bug target/114606] " cvs-commit at gcc dot gnu.org
2024-04-10 21:28 ` mpolacek at gcc dot gnu.org

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).