From: "Richard Guenther" <richard.guenther@gmail.com>
To: "Rob Quill" <rob.quill@gmail.com>
Cc: "Ian Lance Taylor" <iant@google.com>,
"Diego Novillo" <dnovillo@google.com>,
gcc-patches@gcc.gnu.org, "Ben Elliston" <bje@air.net.au>
Subject: Re: Scripted pass manager
Date: Wed, 05 Dec 2007 18:41:00 -0000 [thread overview]
Message-ID: <84fc9c000712051041v1f7ce1b7u4cbaa3d7ebef0a57@mail.gmail.com> (raw)
In-Reply-To: <baf6008d0712051038g61d2d041ob83bf271b1205518@mail.gmail.com>
On Dec 5, 2007 7:38 PM, Rob Quill <rob.quill@gmail.com> wrote:
> On 05 Dec 2007 07:35:35 -0800, Ian Lance Taylor <iant@google.com> wrote:
> > Diego Novillo <dnovillo@google.com> writes:
> >
> > > A scripted pass manager is a step forward, but I think we can go to a
> > > fully dynamic manager.
>
> OK, so do you think it is best to try and start making a scripted pass
> manager, or jump straight into making a dynamic one?
The difference from what we have now should be similar, so I'd jump
straight to the dynamic one. Whatever the exact difference between
a scripted (as in my sense - Diego replied to your original mail) and a
dynamic one is ;)
Richard.
next prev parent reply other threads:[~2007-12-05 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 0:38 Rob Quill
2007-11-27 19:07 ` Richard Guenther
2007-11-27 19:19 ` Basile STARYNKEVITCH
2007-11-29 15:42 ` Richard Guenther
2007-11-29 16:40 ` Ramana Radhakrishnan
2007-11-30 20:04 ` Rob Quill
2007-11-30 20:15 ` Richard Guenther
2007-12-05 0:14 ` Diego Novillo
2007-12-05 0:56 ` Andrew Pinski
2007-12-05 15:36 ` Ian Lance Taylor
2007-12-05 18:38 ` Rob Quill
2007-12-05 18:41 ` Richard Guenther [this message]
2007-12-05 18:42 ` Diego Novillo
[not found] ` <20071205222948.GC24660@air.net.au>
2007-12-06 10:46 ` Rob Quill
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=84fc9c000712051041v1f7ce1b7u4cbaa3d7ebef0a57@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=bje@air.net.au \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=rob.quill@gmail.com \
/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).