On Thu, Apr 2, 2020 at 12:21 PM Martin Jambor <mjam...@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 <mjam...@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 <mjam...@suse.cz>
> +
> + * doc/invoke.texi (Optimize Options): Document sra-max-propagations.
> +
> 2020-04-01 Jakub Jelinek <ja...@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
>
