From: Richard Guenther <richard.guenther@gmail.com>
To: Sebastian Pop <sebpop@gmail.com>
Cc: gcc-patches@gcc.gnu.org, gcc-graphite@googlegroups.com
Subject: Re: [PATCH 06/12] Bump the size of scevs.
Date: Fri, 16 Jul 2010 08:03:00 -0000 [thread overview]
Message-ID: <AANLkTinmXehC53wkum5N_uXSZ7UgWJf4sEvUacEGj47Q@mail.gmail.com> (raw)
In-Reply-To: <1279263843-9149-7-git-send-email-sebpop@gmail.com>
On Fri, Jul 16, 2010 at 9:03 AM, Sebastian Pop <sebpop@gmail.com> wrote:
> 2010-07-15 Sebastian Pop <sebastian.pop@amd.com>
>
> * params.def (PARAM_SCEV_MAX_EXPR_SIZE): Bump the value to 100.
What's the effect on compile-time here?
Richard.
> ---
> gcc/ChangeLog.graphite | 4 ++++
> gcc/params.def | 2 +-
> 2 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/gcc/ChangeLog.graphite b/gcc/ChangeLog.graphite
> index 8408cf2..d75912c 100644
> --- a/gcc/ChangeLog.graphite
> +++ b/gcc/ChangeLog.graphite
> @@ -1,5 +1,9 @@
> 2010-07-15 Sebastian Pop <sebastian.pop@amd.com>
>
> + * params.def (PARAM_SCEV_MAX_EXPR_SIZE): Bump the value to 100.
> +
> +2010-07-15 Sebastian Pop <sebastian.pop@amd.com>
> +
> * cfgloop.c (alloc_loop): Remove initialization of loop->single_iv.
> * cfgloop.h (struct loop): Remove single_iv field.
> * graphite-sese-to-poly.c (graphite_loop_normal_form): Removed.
> diff --git a/gcc/params.def b/gcc/params.def
> index 35650ff..5a91e74 100644
> --- a/gcc/params.def
> +++ b/gcc/params.def
> @@ -438,7 +438,7 @@ DEFPARAM(PARAM_IV_ALWAYS_PRUNE_CAND_SET_BOUND,
> DEFPARAM(PARAM_SCEV_MAX_EXPR_SIZE,
> "scev-max-expr-size",
> "Bound on size of expressions used in the scalar evolutions analyzer",
> - 20, 0, 0)
> + 100, 0, 0)
>
> DEFPARAM(PARAM_OMEGA_MAX_VARS,
> "omega-max-vars",
> --
> 1.7.0.4
>
>
next prev parent reply other threads:[~2010-07-16 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 7:04 [PATCH 00/12] [graphite] Remove the induction variable canonicalization Sebastian Pop
2010-07-16 7:04 ` [PATCH 03/12] chrec_apply should only apply to the specified variable Sebastian Pop
2010-07-16 7:04 ` [PATCH 07/12] Scevs could be expressions without chrecs and still be scev_analyzable_p Sebastian Pop
2010-07-16 7:04 ` [PATCH 09/12] Add testcase for PR42729 and fix handling of gimple_debug info Sebastian Pop
2010-07-16 7:05 ` [PATCH 01/12] Remove insert_loop_close_phis Sebastian Pop
2010-07-16 7:05 ` [PATCH 05/12] Remove uses of loop->single_iv Sebastian Pop
2010-07-16 7:05 ` [PATCH 08/12] Special case non close-phi nodes with one argument in rewrite_close_phi_out_of_ssa Sebastian Pop
2010-07-16 7:05 ` [PATCH 12/12] Unshare the scev before code generating it Sebastian Pop
2010-07-16 7:05 ` [PATCH 11/12] Do not rewrite out of SSA scalar phi nodes that can be scev_analyzable_p Sebastian Pop
2010-07-16 7:05 ` [PATCH 06/12] Bump the size of scevs Sebastian Pop
2010-07-16 8:03 ` Richard Guenther [this message]
2010-07-16 14:41 ` Sebastian Pop
2010-07-16 7:05 ` [PATCH 10/12] Correctly handle SSA_NAME_IS_DEFAULT_DEF in rewrite_close_phi_out_of_ssa Sebastian Pop
2010-07-16 7:05 ` [PATCH 02/12] Remove expand_scalar_variables_ hack Sebastian Pop
2010-07-16 7:05 ` [PATCH 04/12] Also handle GIMPLE_CALLs in rewrite_cross_bb_scalar_deps Sebastian Pop
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=AANLkTinmXehC53wkum5N_uXSZ7UgWJf4sEvUacEGj47Q@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-graphite@googlegroups.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sebpop@gmail.com \
/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).