aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-ssa-loop-niter.c
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2020-04-02 14:34:42 +0200
committerJakub Jelinek <jakub@redhat.com>2020-04-02 14:34:42 +0200
commit86c924113208f58fdda24078c9cc9285ee8000cd (patch)
tree027b39fd9d2cf566cce6ec370e49a786fede44ca /gcc/tree-ssa-loop-niter.c
parent2c0fa3ecf70d199af18785702e9e0548fd3ab793 (diff)
downloadgcc-86c924113208f58fdda24078c9cc9285ee8000cd.zip
gcc-86c924113208f58fdda24078c9cc9285ee8000cd.tar.gz
gcc-86c924113208f58fdda24078c9cc9285ee8000cd.tar.bz2
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.
Diffstat (limited to 'gcc/tree-ssa-loop-niter.c')
0 files changed, 0 insertions, 0 deletions