From: Martin Jambor <mjambor@suse.cz>
Date: Thu, 2 Apr 2020 13:11:22 +0000 (+0200)
Subject: sra/doc: Document param sra-max-propagations
X-Git-Tag: basepoints/gcc-11~561
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d4ed2cd13d0277b5e2c1dc1d1da998a631053cd8;p=thirdparty%2Fgcc.git

sra/doc: Document param sra-max-propagations

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.
---

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 3ffac6702ada..3e3f1ea13c75 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-02  Jakub Jelinek  <jakub@redhat.com>
 
 	PR rtl-optimization/92264
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 412750c1fc96..e9e1683e9a87 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