* [PATCH] sra/doc: Document param sra-max-propagations
@ 2020-04-02 10:20 Martin Jambor
2020-04-02 10:36 ` Richard Biener
0 siblings, 1 reply; 2+ messages in thread
From: Martin Jambor @ 2020-04-02 10:20 UTC (permalink / raw)
To: GCC Patches
Hi,
I forgot to document the new param in invoke.texi, does the text below
look 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] sra/doc: Document param sra-max-propagations
2020-04-02 10:20 [PATCH] sra/doc: Document param sra-max-propagations Martin Jambor
@ 2020-04-02 10:36 ` Richard Biener
0 siblings, 0 replies; 2+ messages in thread
From: Richard Biener @ 2020-04-02 10:36 UTC (permalink / raw)
To: Martin Jambor; +Cc: GCC Patches
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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-04-02 10:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-02 10:20 [PATCH] sra/doc: Document param sra-max-propagations Martin Jambor
2020-04-02 10:36 ` Richard Biener
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).