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)] enable strub for all viable functions by default, for testing Date: Thu, 8 Jun 2023 04:48:46 +0000 (GMT) [thread overview] Message-ID: <20230608044846.7BF7E385734A@sourceware.org> (raw) https://gcc.gnu.org/g:c33ae460294a5837bed448073c09a80c2b76a814 commit c33ae460294a5837bed448073c09a80c2b76a814 Author: Alexandre Oliva <oliva@adacore.com> Date: Thu Jul 28 03:30:22 2022 -0300 enable strub for all viable functions by default, for testing Diff: --- gcc/common.opt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/common.opt b/gcc/common.opt index e798f14d2ba..3bd3ed49ba8 100644 --- a/gcc/common.opt +++ b/gcc/common.opt @@ -2859,7 +2859,7 @@ Enable stack scrub as per attributes, with strict call checking. ; 0 if no strub-enabling attribute is seen. This minimizes the strub ; overhead. fstrub=relaxed -Common RejectNegative Var(flag_strub, -3) Init(-3) +Common RejectNegative Var(flag_strub, -3) Init(3) ; alt default for testing. Restore default strub mode: as per attributes, with relaxed checking. fstrub=all
next reply other threads:[~2023-06-08 4:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-08 4:48 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-11-20 10:47 Alexandre Oliva 2023-10-06 5:26 Alexandre Oliva 2023-06-09 11:26 Alexandre Oliva 2023-06-09 6:18 Alexandre Oliva 2023-06-08 11:00 Alexandre Oliva 2023-06-08 10:44 Alexandre Oliva 2023-06-08 9:18 Alexandre Oliva 2022-07-28 6:39 Alexandre Oliva 2022-05-06 5:51 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=20230608044846.7BF7E385734A@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: 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).