public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "firasuke at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/100826] New: Add that "-fgcse-after-reload" is enabled at "-O3"
Date: Sat, 29 May 2021 12:13:15 +0000	[thread overview]
Message-ID: <bug-100826-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100826
           Summary: Add that "-fgcse-after-reload" is enabled at "-O3"
           Product: gcc
           Version: 11.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: firasuke at gmail dot com
  Target Milestone: ---

Hello there,

Upon reading the GCC manual I stumbled upon the following flag
`-fgcse-after-reload`, which happens to be mentioned twice, the first time
being at:

```
       -O3 Optimize yet more.  -O3 turns on all optimizations specified by -O2
and also turns on the following optimization flags:

           -fgcse-after-reload -fipa-cp-clone ...
```

and the second time:

```
       -fgcse-after-reload
           When -fgcse-after-reload is enabled, a redundant load elimination
pass is performed after reload.  The purpose of this pass is to clean up
redundant
           spilling.

           Enabled by -fprofile-use and -fauto-profile.
```

I think it'd be better if the following statement:

"Enabled by -fprofile-use and -fauto-profile."

be changed to:

"Enabled by -O3, -fprofile-use, and -fauto-profile."

to show that it is also enabled by `-O3`, similar to `-fpeel-loops`.

Thanks in advance!

             reply	other threads:[~2021-05-29 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 12:13 firasuke at gmail dot com [this message]
2021-05-31  8:44 ` [Bug other/100826] " marxin at gcc dot gnu.org
2021-06-01 12:21 ` cvs-commit at gcc dot gnu.org
2021-06-01 12:22 ` marxin at gcc dot gnu.org
2021-06-01 13:53 ` firasuke at gmail dot com
2021-06-01 13:59 ` marxin at gcc dot gnu.org
2021-09-17  6:43 ` pinskia at gcc dot gnu.org

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=bug-100826-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).