linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Sheridan <djs@postman.org.uk>
To: Josh Triplett <josh@freedesktop.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 0/2] Improved flow graphs
Date: Tue, 29 May 2007 17:05:10 +0100	[thread overview]
Message-ID: <1180454712.5068.49.camel@localhost.localdomain> (raw)
In-Reply-To: <46536AA6.20604@freedesktop.org>

On Tue, 2007-05-22 at 15:11 -0700, Josh Triplett wrote:
> Dan Sheridan wrote:
> > These two patches are the first of several implementing improved graph
> > generation for Sparse.
> 
> Very nice work.  I've applied both patches in this series.

Thanks.

> I noticed one minor issue: gvpr/return-paths seems to turn some internal
> edges in functions into dotted-line return paths.

I think you are talking about the edges which connect call sites to
return sites. These are needed to keep the layout of the graph sane, but
could be made invisible. It would at least help if they looked different
to the return edges.

> Also, unprocessed graphs have now become far more messy; for instance,
> graphing validation/context.c generates numerous edges to a() and r().  Any
> way you could prevent these edges from crossing other subgraphs? 

Probably not. There's a lot of tweaking possible with weights, which
I'll experiment with a bit, but your suggestion of separate a() and r()
nodes might be simpler. Should be very easy to obtain with a gvpr
script.

	Dan.

      reply	other threads:[~2007-05-29 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 10:11 [PATCH 0/2] Improved flow graphs Dan Sheridan
2007-05-16 18:03 ` Anderson Lizardo
2007-05-22 22:11 ` Josh Triplett
2007-05-29 16:05   ` Dan Sheridan [this message]

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=1180454712.5068.49.camel@localhost.localdomain \
    --to=djs@postman.org.uk \
    --cc=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.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).