public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: Steven Bosscher <stevenb@suse.de>
Cc: gcc@gcc.gnu.org
Subject: [scev] Re: Strange IV choices?
Date: Tue, 14 Dec 2004 15:22:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0412141619440.4584-100000@alwazn.tat.physik.uni-tuebingen.de> (raw)
In-Reply-To: <3465883.1103037220381.SLOX.WebMail.wwwrun@extimap.suse.de>

On Tue, 14 Dec 2004, Steven Bosscher wrote:

> On Dec 14, 2004 04:02 PM, Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> wrote:
> > No, but does this help the scev analyzer with currently
> > unknown evolution?

It seems to depend on the level of "indirection" in the C++ class
hierarchy, if I short-cut one level, it works again.  Are there
any complexity limits in the scev analyzer?  How would they depend
on the amount of "local" variables?

I'm slightly confused.  Maybe someone can have a look at the ivopts dump.

> No.  I misread your mail as just another "IVOPTS sucks" mail,
> sorry about that.

No problem.

Richard.

--
Richard Guenther <richard dot guenther at uni-tuebingen dot de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/

  reply	other threads:[~2004-12-14 15:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 14:56 Richard Guenther
2004-12-14 15:01 ` Steven Bosscher
2004-12-14 15:02   ` Richard Guenther
2004-12-14 15:13     ` Steven Bosscher
2004-12-14 15:22       ` Richard Guenther [this message]
2004-12-14 15:38         ` [scev] " Richard Guenther
2004-12-15 15:51 ` Sebastian Pop
2004-12-15 16:36   ` Richard Guenther
2004-12-15 16:55   ` Giovanni Bajo

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=Pine.LNX.4.44.0412141619440.4584-100000@alwazn.tat.physik.uni-tuebingen.de \
    --to=rguenth@tat.physik.uni-tuebingen.de \
    --cc=gcc@gcc.gnu.org \
    --cc=stevenb@suse.de \
    /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).