params: Decrease -param=max-find-base-term-values= default [PR92264]

For the PR in question, my proposal would be to also lower
-param=max-find-base-term-values=
default from 2000 to 200 after this, at least in the above 4
bootstraps/regtests there is nothing that would ever result in
find_base_term returning non-NULL with more than 200 VALUEs being processed.

2020-04-02  Jakub Jelinek  <jakub@redhat.com>

	PR rtl-optimization/92264
	* params.opt (-param=max-find-base-term-values=): Decrease default
	from 2000 to 200.

gcc/ChangeLog

 2020-04-02  Jakub Jelinek  <jakub@redhat.com>
 
 	PR rtl-optimization/92264
+	* params.opt (-param=max-find-base-term-values=): Decrease default
+	from 2000 to 200.
+
+	PR rtl-optimization/92264
 	* rtl.h (struct rtx_def): Mention that call bit is used as
 	SP_DERIVED_VALUE_P in cselib.c.
 	* cselib.c (SP_DERIVED_VALUE_P): Define.

gcc/params.opt

@@ -663,7 +663,7 @@ Common Joined UInteger Var(param_max_vartrack_size) Init(50000000) Param Optimiz
 Max. size of var tracking hash tables.
 
 -param=max-find-base-term-values=
-Common Joined UInteger Var(param_max_find_base_term_values) Init(2000) Param Optimization
+Common Joined UInteger Var(param_max_find_base_term_values) Init(200) Param Optimization
 Maximum number of VALUEs handled during a single find_base_term call.
 
 -param=max-vrp-switch-assertions=