public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-10093] Remove repeated information in -ftree-loop-distribute-patterns doc Date: Tue, 23 Apr 2024 13:51:59 +0000 (GMT) [thread overview] Message-ID: <20240423135159.2415D3858C50@sourceware.org> (raw) https://gcc.gnu.org/g:6f0a646dd2fc59e9c9cde63718b36085f84a19ba commit r14-10093-g6f0a646dd2fc59e9c9cde63718b36085f84a19ba Author: Jan Hubicka <jh@suse.cz> Date: Tue Apr 23 15:51:42 2024 +0200 Remove repeated information in -ftree-loop-distribute-patterns doc We have: -ftree-loop-distribute-patterns Perform loop distribution of patterns that can be code generated with calls to a library. This flag is enabled by default at -O2 and higher, and by -fprofile-use and -fauto-profile. This pass distributes the initialization loops and generates a call to memset zero. For example, the loop ... and the initialization loop is transformed into a call to memset zero. This flag is enabled by default at -O3. It is also enabled by -fprofile-use and -fauto-profile. Which mentions optimizatoin flags twice and the repeated mention is out of date, since we enable this option at -O2 as well. gcc/ChangeLog: * doc/invoke.texi (-ftree-loop-distribute-patterns): Remove duplicated sentence about optimization flags implying this. Diff: --- gcc/doc/invoke.texi | 2 -- 1 file changed, 2 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 2a35dc7ac75..27c31ab0c86 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -13852,8 +13852,6 @@ DO I = 1, N ENDDO @end smallexample and the initialization loop is transformed into a call to memset zero. -This flag is enabled by default at @option{-O3}. -It is also enabled by @option{-fprofile-use} and @option{-fauto-profile}. @opindex floop-interchange @item -floop-interchange
reply other threads:[~2024-04-23 13:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240423135159.2415D3858C50@sourceware.org \ --to=hubicka@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).