linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Dibyendu Majumdar <mobile@majumdar.org.uk>,
	Linux-Sparse <linux-sparse@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Simple SSA status
Date: Thu, 7 Sep 2017 06:24:29 +0200	[thread overview]
Message-ID: <CAExDi1RYam46QLnd+i4zCF-CkfEoTXaWHwY6t=VjqFAsTYV9Eg@mail.gmail.com> (raw)
In-Reply-To: <CANeU7QkPX30OHb_GLqDv=22YJ6aAY5KCe55=QJ17fbNaFqtFVA@mail.gmail.com>

On Thu, Sep 7, 2017 at 6:02 AM, Christopher Li <sparse@chrisli.org> wrote:
> On Wed, Sep 6, 2017 at 11:46 PM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
>
>>> For reducible graph that algorithm converge in constant iteration.
>>
>> Where the 'constant' is a function of the loop complexity (maximum
>> nesting level) ...
>
> I think we are talking different things.

Since you're talking performance and complexity, I suggest that you read
carefully the section "Complexity Analysis" of the article and look where
it's written 'd(G)' and 'loop connectedness'.

-- Luc

  reply	other threads:[~2017-09-07  4:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 19:39 master merge plans Christopher Li
2017-08-22 13:32 ` Luc Van Oostenryck
2017-08-22 14:47   ` Christopher Li
2017-08-22 15:51     ` Christopher Li
2017-08-22 20:05       ` Luc Van Oostenryck
2017-08-23 20:50         ` Christopher Li
2017-08-29 11:27           ` Christopher Li
2017-09-03 19:24             ` Luc Van Oostenryck
2017-08-22 14:53   ` Dibyendu Majumdar
2017-08-22 14:59     ` Christopher Li
2017-09-03 20:26       ` Simple SSA status Luc Van Oostenryck
2017-09-04 18:29         ` Christopher Li
2017-09-04 20:07           ` Luc Van Oostenryck
2017-09-04 20:37             ` Dibyendu Majumdar
2017-09-04 20:55               ` Luc Van Oostenryck
2017-09-04 21:24                 ` Dibyendu Majumdar
2017-09-04 23:31             ` Christopher Li
2017-09-05  0:55               ` Luc Van Oostenryck
2017-09-05  3:28                 ` Christopher Li
2017-09-07  2:03                   ` Luc Van Oostenryck
2017-09-07  2:15                     ` Linus Torvalds
2017-09-07  2:55                       ` Christopher Li
2017-09-07  3:17                         ` Luc Van Oostenryck
2017-09-07  4:04                           ` Christopher Li
2017-09-07  4:49                             ` Luc Van Oostenryck
2017-09-07  6:17                               ` Christopher Li
2017-09-07  7:38                                 ` Luc Van Oostenryck
2017-09-07  3:05                       ` Luc Van Oostenryck
2017-09-07  2:20                     ` Christopher Li
2017-09-07  3:46                       ` Luc Van Oostenryck
2017-09-07  4:02                         ` Christopher Li
2017-09-07  4:24                           ` Luc Van Oostenryck [this message]
2017-09-07  4:33                             ` Christopher Li

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='CAExDi1RYam46QLnd+i4zCF-CkfEoTXaWHwY6t=VjqFAsTYV9Eg@mail.gmail.com' \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=mobile@majumdar.org.uk \
    --cc=sparse@chrisli.org \
    --cc=torvalds@linux-foundation.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 NNTP newsgroup(s).