public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] sra/doc: Document param sra-max-propagations
Date: Thu, 2 Apr 2020 12:36:18 +0200	[thread overview]
Message-ID: <CAFiYyc3QFwHQpoWiJ8mX9nJ+mPUkc6Fk+j4Rj_A+FzhCHExDFQ@mail.gmail.com> (raw)
In-Reply-To: <ri64ku29ojz.fsf@suse.cz>

On Thu, Apr 2, 2020 at 12:21 PM Martin Jambor <mjambor@suse.cz> wrote:
>
> Hi,
>
> I forgot to document the new param in invoke.texi, does the text below
> look OK?

OK.

> Tested with make info and make pdf.
>
> Thanks,
>
> Martin
>
>
> 2020-04-02  Martin Jambor  <mjambor@suse.cz>
>
>         * doc/invoke.texi (Optimize Options): Document sra-max-propagations.
> ---
>  gcc/ChangeLog       | 4 ++++
>  gcc/doc/invoke.texi | 5 +++++
>  2 files changed, 9 insertions(+)
>
> diff --git a/gcc/ChangeLog b/gcc/ChangeLog
> index 654356c8dc8..a93db199cf9 100644
> --- a/gcc/ChangeLog
> +++ b/gcc/ChangeLog
> @@ -1,3 +1,7 @@
> +2020-04-02  Martin Jambor  <mjambor@suse.cz>
> +
> +       * doc/invoke.texi (Optimize Options): Document sra-max-propagations.
> +
>  2020-04-01  Jakub Jelinek  <jakub@redhat.com>
>
>         PR middle-end/94423
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index 412750c1fc9..e9e1683e9a8 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -12785,6 +12785,11 @@ speed
>  (@option{sra-max-scalarization-size-Ospeed}) or size
>  (@option{sra-max-scalarization-size-Osize}) respectively.
>
> +@item sra-max-propagations
> +The maximum number of artificial accesses that Scalar Replacement of
> +Aggregates (SRA) will track, per one local variable, in order to
> +facilitate copy propagation.
> +
>  @item tm-max-aggregate-size
>  When making copies of thread-local variables in a transaction, this
>  parameter specifies the size in bytes after which variables are
> --
> 2.25.1
>

      reply	other threads:[~2020-04-02 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 10:20 Martin Jambor
2020-04-02 10:36 ` Richard Biener [this message]

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=CAFiYyc3QFwHQpoWiJ8mX9nJ+mPUkc6Fk+j4Rj_A+FzhCHExDFQ@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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).