public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nils.smeds at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/103438] New: Updated documentation for gcc Optimization command line options (sec 3.11)
Date: Fri, 26 Nov 2021 11:27:18 +0000	[thread overview]
Message-ID: <bug-103438-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103438
           Summary: Updated documentation for gcc Optimization command
                    line options (sec 3.11)
           Product: gcc
           Version: 11.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nils.smeds at gmail dot com
  Target Milestone: ---

Created attachment 51880
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51880&action=edit
Patch to file gcc/doc/invoke.texi

I was confused about when options --fprefetch-loop-arrays and
--aggressive-loop-optimizations are active and found that these options are
always active (including at level -O0). So I took a pass through the
documentation page and made it reflect this.

I changed the wording for -Os as it to some extent contradicted the options
actually in effect at -Os

I also made minor edits to make chapter 3.11 more consistent in formatting, in
particular making sure that "Enabled/Disabled..." information at the end of
parameter sections is a separate paragraph.

Hope it will be useful

             reply	other threads:[~2021-11-26 11:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 11:27 nils.smeds at gmail dot com [this message]
2021-11-26 11:35 ` [Bug middle-end/103438] " pinskia at gcc dot gnu.org
2021-11-26 11:36 ` redi at gcc dot gnu.org
2021-11-26 11:37 ` pinskia at gcc dot gnu.org
2021-11-26 11:48 ` nils.smeds at gmail dot com
2021-11-26 12:35 ` rguenth at gcc dot gnu.org
2021-11-26 12:46 ` marxin at gcc dot gnu.org
2021-11-26 13:20 ` nils.smeds at gmail dot com
2021-11-26 21:42 ` nils.smeds at gmail dot com
2021-11-29 15:17 ` marxin at gcc dot gnu.org
2021-12-02 12:56 ` nils.smeds at gmail dot com
2021-12-02 13:32 ` nils.smeds at gmail dot com
2021-12-02 14:02 ` marxin at gcc dot gnu.org
2021-12-02 14:03 ` nils.smeds at gmail dot com
2021-12-02 14:06 ` nils.smeds at gmail dot com
2021-12-07 13:38 ` cvs-commit at gcc dot gnu.org
2021-12-07 13:39 ` marxin at gcc dot gnu.org
2022-07-08 12:51 ` marxin 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-103438-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).