public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] hardcfr: optionally disable in leaf functions
Date: Thu, 20 Oct 2022 22:32:28 +0000 (GMT)	[thread overview]
Message-ID: <20221020223228.6026F383DB8E@sourceware.org> (raw)

https://gcc.gnu.org/g:146acff55ad3d82128d95b1fc481ca2debe75550

commit 146acff55ad3d82128d95b1fc481ca2debe75550
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed Oct 19 20:36:30 2022 -0300

    hardcfr: optionally disable in leaf functions
    
    Introduce -fhardcfr-skip-leaf to avoid control flow redundancy
    instrumentation of leaf functions, where the benefit is far more
    limited.
    
    
    for  gcc/ChangeLog
    
            * common.opt (fhardcfr-skip-leaf): New.
            * doc/invoke.texi: Document it.
            * gimple-harden-control-flow.cc
            (pass_harden_control_flow_redundancy::execute): Honor it.
    
    for  gcc/testsuite/ChangeLog
    
            * c-c++-common/torture/harden-cfr-skip-leaf.c: New.

Diff:
---
 gcc/common.opt                                     |  4 ++++
 gcc/doc/invoke.texi                                |  7 +++++-
 gcc/gimple-harden-control-flow.cc                  | 27 ++++++++++++++++++++++
 .../c-c++-common/torture/harden-cfr-skip-leaf.c    | 10 ++++++++
 4 files changed, 47 insertions(+), 1 deletion(-)

diff --git a/gcc/common.opt b/gcc/common.opt
index e57646ce125..1f929428bc0 100644
--- a/gcc/common.opt
+++ b/gcc/common.opt
@@ -1798,6 +1798,10 @@ fharden-control-flow-redundancy
 Common Var(flag_harden_control_flow_redundancy) Optimization
 Harden control flow by recording and checking execution paths.
 
+fhardcfr-skip-leaf
+Common Var(flag_harden_control_flow_redundancy_skip_leaf) Optimization
+Disable CFR in leaf functions.
+
 fhardcfr-check-returning-calls
 Common Var(flag_harden_control_flow_redundancy_check_returning_calls) Init(-1) Optimization
 Check CFR execution paths also before calls followed by returns of their results.
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 24ff8e36721..427006608af 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -627,7 +627,8 @@ Objective-C and Objective-C++ Dialects}.
 -fsanitize-undefined-trap-on-error  -fbounds-check @gol
 -fcf-protection=@r{[}full@r{|}branch@r{|}return@r{|}none@r{|}check@r{]} @gol
 -fharden-compares -fharden-conditional-branches @gol
--fharden-control-flow-redundancy  -fhardcfr-check-exceptions  @gol
+-fharden-control-flow-redundancy  -fhardcfr-skip-leaf  @gol
+-fhardcfr-check-exceptions  @gol
 -fhardcfr-check-returning-calls  @gol
 -fhardcfr-check-noreturn-calls=@r{[}always@r{|}nothrow@r{|}never@r{]}  @gol
 -fstack-protector  -fstack-protector-all  -fstack-protector-strong @gol
@@ -16664,6 +16665,10 @@ would also have verification issued before the call, but these
 possibilities are merely theoretical, as these conditions can only be
 met when using custom compiler plugins.
 
+@item -fhardcfr-skip-leaf
+@opindex fhardcfr-skip-leaf
+Disable @option{-fharden-control-flow-redundancy} in leaf functions.
+
 @item -fhardcfr-check-exceptions
 @opindex fhardcfr-check-exceptions
 @opindex fno-hardcfr-check-exceptions
diff --git a/gcc/gimple-harden-control-flow.cc b/gcc/gimple-harden-control-flow.cc
index 862cdd45eaf..dfebb8296ed 100644
--- a/gcc/gimple-harden-control-flow.cc
+++ b/gcc/gimple-harden-control-flow.cc
@@ -1114,6 +1114,33 @@ pass_harden_control_flow_redundancy::execute (function *fun)
   basic_block bb;
   basic_block bb_eh_cleanup = NULL;
 
+  if (flag_harden_control_flow_redundancy_skip_leaf)
+    {
+      bool found_calls_p = false;
+
+      FOR_EACH_BB_FN (bb, fun)
+	{
+	  for (gimple_stmt_iterator gsi = gsi_last_bb (bb);
+	       !gsi_end_p (gsi); gsi_prev (&gsi))
+	    if (is_a <gcall *> (gsi_stmt (gsi)))
+	      {
+		found_calls_p = true;
+		break;
+	      }
+	  if (found_calls_p)
+	    break;
+	}
+
+      if (!found_calls_p)
+	{
+	  if (dump_file)
+	    fprintf (dump_file,
+		     "Disabling CFR for leaf function, as requested\n");
+
+	  return 0;
+	}
+    }
+
   if (check_at_escaping_exceptions)
     {
       int lp_eh_cleanup = -1;
diff --git a/gcc/testsuite/c-c++-common/torture/harden-cfr-skip-leaf.c b/gcc/testsuite/c-c++-common/torture/harden-cfr-skip-leaf.c
new file mode 100644
index 00000000000..85ecaa04d04
--- /dev/null
+++ b/gcc/testsuite/c-c++-common/torture/harden-cfr-skip-leaf.c
@@ -0,0 +1,10 @@
+/* { dg-do run } */
+/* { dg-options "-fharden-control-flow-redundancy -fhardcfr-skip-leaf -fdump-tree-hardcfr -ffat-lto-objects" } */
+
+/* Test skipping instrumentation of leaf functions.  */
+
+#include "harden-cfr.c"
+
+/* { dg-final { scan-tree-dump-times "__builtin_trap" 0 "hardcfr" } } */
+/* Only main isn't leaf.  */
+/* { dg-final { scan-tree-dump-times "__hardcfr_check" 2 "hardcfr" } } */

             reply	other threads:[~2022-10-20 22:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 22:32 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-23 20:13 Alexandre Oliva
2023-06-09  8:07 Alexandre Oliva
2023-06-09  6:17 Alexandre Oliva
2023-06-08 10:59 Alexandre Oliva
2023-06-08 10:43 Alexandre Oliva
2023-06-08  9:17 Alexandre Oliva
2023-06-08  4:48 Alexandre Oliva
2022-10-25  2:52 Alexandre Oliva
2022-10-20  5:46 Alexandre Oliva
2022-10-20  4:09 Alexandre Oliva

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=20221020223228.6026F383DB8E@sourceware.org \
    --to=aoliva@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: 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).