public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr>
To: Jan Hubicka <jh@suse.cz>
Cc: gcc@gcc.gnu.org
Subject: Re: [RFC] CFG hooks for rtl/tree specificities
Date: Tue, 01 Apr 2003 17:05:00 -0000	[thread overview]
Message-ID: <20030401161112.GD24512@gauvain.u-strasbg.fr> (raw)
In-Reply-To: <20030401154607.GF904@kam.mff.cuni.cz>

On Tue, Apr 01, 2003 at 05:46:07PM +0200, Jan Hubicka wrote:
> 
> This looks nice.
> It would be interesting to think about what operations do we really need
> - for instance split_edge should be probably implementable already via
> the primitive operations (basic block creation, edge redirection).  Our

Yes, the split_edge function is trivially implemented at the tree level:

basic_block
tree_split_edge (edge_in)
     edge edge_in;
{
  basic_block new_bb, dest;
  
  /* Abnormal edges cannot be split.  */
  if (edge_in->flags & EDGE_ABNORMAL)
    abort ();
  
  dest = edge_in->dest;
  new_bb = create_bb ();
  redirect_edge_succ  (edge_in, new_bb);
  make_edge (new_bb, dest, EDGE_FALLTHRU);
  return new_bb;
}

except "create_bb" all the other functions are CFG generic, making the split_edge
a good candidate for the CFG API.  At RTL level the split_edge function deals
with insns at this moment.

> current API is not 100% ready for that so we will probably need cleanup
> on the way.
> 
> I would be happy about switching to the hooks first and leaving it to me
> to cleanup the APIs if you preffer.
> 
Yes, thanks.

Sebastian

  reply	other threads:[~2003-04-01 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 16:11 Pop Sébastian
2003-04-01 16:23 ` Jan Hubicka
2003-04-01 17:05   ` Pop Sébastian [this message]
2003-04-01 17:08     ` Jan Hubicka
2003-04-01 18:12     ` Diego Novillo
2003-04-02 14:19       ` Pop Sébastian
2003-06-14 13:13         ` Jan Hubicka
2003-06-14 19:42           ` Pop Sébastian
2003-06-14 21:01             ` Jan Hubicka
2003-06-15 16:38               ` Jan Hubicka

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=20030401161112.GD24512@gauvain.u-strasbg.fr \
    --to=pop@gauvain.u-strasbg.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    /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).