From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc@gcc.gnu.org>
Subject: [new-ra] Development status?
Date: Sun, 18 Jan 2004 03:13:00 -0000 [thread overview]
Message-ID: <22e301c3dd71$1875c480$34b82997@bagio> (raw)
Hello,
what's the development status for new-ra? How does it look like right now? Does
it improve compile-time or code generation? On which platforms? This has been
also discussed several times on IRC with mixed results, so I would like to get
a complete status report for it. The point has been brought up in the tree-ssa
discussion as well.
I would also like to ask why there is an active development branch for new-ra.
We have a few bug reports in bugzilla which are against the mainline version
(-fnew-ra), which looks like to be outdated. Can the development be done on the
mainline directly? Can the latest version be merged to the 3.4 branch &
mainline? Also, we never consider *any* new-ra bug as regressions since it's an
experimental switch for 3.4, so I guess changes can be committed there freely,
without the "regression-only" policy.
Thanks!
Giovanni Bajo
next reply other threads:[~2004-01-18 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 3:13 Giovanni Bajo [this message]
2004-01-19 9:58 ` Michael Matz
2004-01-20 16:35 ` Denis Chertykov
2004-01-20 16:48 ` Michael Matz
2004-01-20 17:26 ` Denis Chertykov
2004-01-21 14:11 ` Michael Matz
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='22e301c3dd71$1875c480$34b82997@bagio' \
--to=giovannibajo@libero.it \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).