public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard@codesourcery.com>
To: "Vladimir N. Makarov" <vmakarov@redhat.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
	  gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: dataflow branch merging plans.
Date: Fri, 25 May 2007 17:15:00 -0000	[thread overview]
Message-ID: <87veegyjp8.fsf@firetop.home> (raw)
In-Reply-To: <4656F755.3000702@redhat.com> (Vladimir N. Makarov's message of 	"Fri, 25 May 2007 10:48:53 -0400")

"Vladimir N. Makarov" <vmakarov@redhat.com> writes:
> <stevenb> honza: you know vlad... he has great ideas, in theory, but there's a reason why he never manages to actually finish something properly ;-)
> <honza> hmm, for example dfa automatos does their job relatively well...
> <stevenb> ...if you're willing to accept that:
> <stevenb> a) it takes 30% of the total compile time
> <stevenb> b) all the good parts are written by zack
> <stevenb> c) all the scheduler descriptions except itanium are written by me
> <stevenb> (oh, and mips, which paolo bonzini took care of)

I know this wasn't meant to be taken seriously, but since Vlad has
already dissed (a) and (b), I don't think (c) is true either.
I'm not aware that Paolo wrote any of the MIPS scheduler descriptions.
(Forgive me if I'm wrong Paolo.)  The define_function_unit-to-DFA
conversion was done my Eric and myself, and the DFA-from-scratch
schedulers were written by an unholy alliance of Eric, Mike Meissner,
David Ung, Joseph Myers and me.  (Sorry again if I've missed anyone.)

And for the record, it's just as well the above wasn't meant to be
taken seriously, as I think it would do Vlad a great disservice.

Richard

  reply	other threads:[~2007-05-25 16:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 13:19 Kenneth Zadeck
2007-05-24  1:29 ` Andrew_Pinski
2007-05-24  7:51   ` Paolo Bonzini
2007-05-24  8:12     ` Paolo Bonzini
2007-05-24 11:47 ` Bernd Schmidt
2007-05-24 20:02   ` Kenneth Zadeck
2007-05-25  9:51     ` Bernd Schmidt
2007-05-25 10:32       ` Paolo Bonzini
2007-05-25 13:00       ` Kenneth Zadeck
2007-05-28 20:55       ` Mark Mitchell
2007-05-29  1:16         ` Kenneth Zadeck
2007-05-29 15:58           ` Mark Mitchell
2007-05-24 21:09   ` Steven Bosscher
2007-05-24 22:23     ` Vladimir N. Makarov
2007-05-24 23:03       ` Steven Bosscher
2007-05-25 13:50         ` Vladimir N. Makarov
2007-05-25 17:15           ` Richard Sandiford [this message]
2007-05-25 18:21             ` Jan Hubicka
2007-05-25 20:13             ` Steven Bosscher
2007-05-25 20:11           ` Steven Bosscher
     [not found] <OF781E582C.3916D180-ON882572E5.00078CD6-882572E5.00082C95@LocalDomain>
2007-05-25  0:12 ` Andrew_Pinski
2007-05-25 19:04 Zack Weinberg
     [not found] <OF1BD0F1DA.E933CF3F-ON422572E9.006B2EF9-422572E9.006B85BF@de.ibm.com>
2007-05-29  1:05 ` Kenneth Zadeck
2007-05-30 13:11   ` Andreas Krebbel1
2007-05-30 14:17     ` Kenneth Zadeck

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=87veegyjp8.fsf@firetop.home \
    --to=richard@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=stevenb.gcc@gmail.com \
    --cc=vmakarov@redhat.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).