From: Diego Novillo <dnovillo@redhat.com>
To: Lars Segerlund <lars.segerlund@comsys.se>
Cc: gcc@gcc.gnu.org
Subject: Re: status of the tree-ssa branch ?
Date: Tue, 14 Jan 2003 19:52:00 -0000 [thread overview]
Message-ID: <20030114150545.GA11757@tornado.toronto.redhat.com> (raw)
In-Reply-To: <3E22CA64.8020500@comsys.se>
On Mon, 13 Jan 2003, Lars Segerlund wrote:
> first, when is it 'scheduled' :-) to be included/merged with 3.x ( and
> which 3.x
>
We are hoping to have something ready for 3.5. As usual, the
canonical answer applies (when it's ready).
> second, is the tree representation likely to undergo further major
> changes ?
>
Not likely. But we only have converted two front ends to GIMPLE
(C and C++). So, new front ends might introduce changes.
> third, if I want to make a front end for gcc is this the 'future safe'
> branch ?
>
I would like to think so. We first need to prove that the
optimization and analyses we do on trees give positive results.
Diego.
prev parent reply other threads:[~2003-01-14 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 16:21 Lars Segerlund
2003-01-14 19:52 ` 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=20030114150545.GA11757@tornado.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=lars.segerlund@comsys.se \
/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).