public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Andrew MacLeod <amacleod@redhat.com>
Subject: [PATCH (pushed)] docs: port documentation of VRP params
Date: Tue, 2 May 2023 14:36:07 +0200	[thread overview]
Message-ID: <9fa34cf8-4d1b-bd02-6757-cae0d07be888@suse.cz> (raw)

gcc/ChangeLog:

	* doc/invoke.texi: Update documentation based on param.opt file.
---
  gcc/doc/invoke.texi | 15 +++++++++------
  1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 2f40c58b21c..b92b8576027 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -15988,15 +15988,9 @@ The maximum number of may-defs we analyze when looking for a must-def
  specifying the dynamic type of an object that invokes a virtual call
  we may be able to devirtualize speculatively.
  
-@item evrp-sparse-threshold
-Maximum number of basic blocks before EVRP uses a sparse cache.
-
  @item ranger-debug
  Specifies the type of debug output to be issued for ranges.
  
-@item evrp-switch-limit
-Specifies the maximum number of switch cases before EVRP ignores a switch.
-
  @item unroll-jam-min-percent
  The minimum percentage of memory references that must be optimized
  away for the unroll-and-jam transformation to be considered profitable.
@@ -16055,6 +16049,15 @@ this parameter.  The default value of this parameter is 50.
  @item vect-induction-float
  Enable loop vectorization of floating point inductions.
  
+@item vrp-sparse-threshold
+Maximum number of basic blocks before VRP uses a sparse bitmap cache.
+
+@item vrp-switch-limit
+Maximum number of outgoing edges in a switch before VRP will not process it.
+
+@item vrp-vector-threshold
+Maximum number of basic blocks for VRP to use a basic cache vector.
+
  @item avoid-fma-max-bits
  Maximum number of bits for which we avoid creating FMAs.
  
-- 
2.40.1


                 reply	other threads:[~2023-05-02 12:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9fa34cf8-4d1b-bd02-6757-cae0d07be888@suse.cz \
    --to=mliska@suse.cz \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@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).