public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Jan Hubicka <jh@suse.cz>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] CFG hooks for rtl/tree specificities
Date: Wed, 02 Apr 2003 14:19:00 -0000	[thread overview]
Message-ID: <20030402122311.GA2708@gauvain.u-strasbg.fr> (raw)
In-Reply-To: <1049214194.1149.26.camel@shadowfax>

On Tue, Apr 01, 2003 at 11:23:12AM -0500, Diego Novillo wrote:
> Note that the edge insertion functions in tree-cfg.c already split
> edges.  If you are going to implement a split_edge routine, could you
> update bsi_commit_first_edge_insert?
> 
Yes.  
That's exactly from where I have took the code for the tree level split_edge.


A question: 
what do you think about extending the basic block iterator (bsi) to handle 
a union {tree, rtl}, then use iterators instead of rtx-es in functions like 
split_block (basic_block, rtx) ?
The implementation (ie. tree_split_block and rtl_split_block) will decide 
wheter the iterator contains a tree or an rtx (C poor man's polymorphism).

Sebastian

  reply	other threads:[~2003-04-02 12:23 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
2003-04-01 17:08     ` Jan Hubicka
2003-04-01 18:12     ` Diego Novillo
2003-04-02 14:19       ` Pop Sébastian [this message]
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=20030402122311.GA2708@gauvain.u-strasbg.fr \
    --to=pop@gauvain.u-strasbg.fr \
    --cc=dnovillo@redhat.com \
    --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).