From: Diego Novillo <dnovillo@redhat.com>
To: nathan@cs.bris.ac.uk
Cc: gcc@gcc.gnu.org
Subject: Re: [ast-optimizer-branch] Merging CFG cleanups from trunk
Date: Wed, 12 Sep 2001 11:51:00 -0000 [thread overview]
Message-ID: <20010912145132.A11564@tornado.cygnus.com> (raw)
In-Reply-To: <3B9FAD9C.2F00DB54@acm.org>
On Wed, 12 Sep 2001, Nathan Sidwell wrote:
> Diego Novillo wrote:
> > There have been some substantial changes to CFG routines in the
> > trunk that affect the tree flowgraph.
> >
> > I'd like to merge those changes into the ast-optimizer-branch to
> > avoid future merging headaches.
> sounds like a good plan. I'm not going to have much time to do things
> on that branch in the near future, so do whatever you think is right
>
Thanks. I will get to it in the next few days.
Diego.
prev parent reply other threads:[~2001-09-12 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 10:17 Diego Novillo
2001-09-12 11:48 ` Nathan Sidwell
2001-09-12 11:51 ` Diego Novillo [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=20010912145132.A11564@tornado.cygnus.com \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=nathan@cs.bris.ac.uk \
/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).