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)] [testing] enable -finline-memset-loops by default Date: Sat, 14 Jan 2023 14:31:34 +0000 (GMT) [thread overview] Message-ID: <20230114143134.36D3E38708F5@sourceware.org> (raw) https://gcc.gnu.org/g:8cfab621b57f9eeedc12ec87234b9629ecff7782 commit 8cfab621b57f9eeedc12ec87234b9629ecff7782 Author: Alexandre Oliva <oliva@gnu.org> Date: Sat Jan 14 08:44:23 2023 -0300 [testing] enable -finline-memset-loops by default Diff: --- gcc/common.opt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/common.opt b/gcc/common.opt index 5d28f054241..2444e1167bc 100644 --- a/gcc/common.opt +++ b/gcc/common.opt @@ -1875,7 +1875,7 @@ Common Var(flag_inline_atomics) Init(1) Optimization Inline __atomic operations when a lock free instruction sequence is available. finline-memset-loops -Common Var(flag_inline_memset_loops) Init(0) Optimization +Common Var(flag_inline_memset_loops) Init(1) Optimization Inline memset even if it requires loops. fcf-protection
next reply other threads:[~2023-01-14 14:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-14 14:31 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-26 8:44 Alexandre Oliva 2023-01-26 8:21 Alexandre Oliva 2023-01-26 8:01 Alexandre Oliva 2023-01-26 7:02 Alexandre Oliva 2023-01-26 6:41 Alexandre Oliva 2023-01-26 6:38 Alexandre Oliva 2023-01-26 6:34 Alexandre Oliva 2023-01-26 6:14 Alexandre Oliva 2023-01-26 6:10 Alexandre Oliva 2023-01-26 5:17 Alexandre Oliva 2023-01-26 4:59 Alexandre Oliva 2023-01-26 3:37 Alexandre Oliva 2023-01-21 1:06 Alexandre Oliva 2023-01-19 6:20 Alexandre Oliva 2023-01-19 4:03 Alexandre Oliva 2023-01-14 12:11 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=20230114143134.36D3E38708F5@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).