public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Kenneth Zadeck <zadeck@naturalbridge.com>
Cc: Bernd Schmidt <bernds_cb1@t-online.de>,
	  gcc-patches <gcc-patches@gcc.gnu.org>,
	 Steven Bosscher <stevenb.gcc@gmail.com>,
	  "Park, Seongbae" <seongbae.park@gmail.com>,
	 "Bonzini, Paolo" <bonzini@gnu.org>,
	  Serge Belyshev <belyshev@depni.sinp.msu.ru>,
	  richard.earnshaw@arm.com,  echristo@apple.com,   "Pinski,
	Andrew" <andrew_pinski@playstation.sony.com>,
	 "Weigand, Ulrich" <Ulrich.Weigand@de.ibm.com>,
	  Ian Lance Taylor <iant@google.com>,
	 "Edelsohn, David" <dje@watson.ibm.com>,
	  "Berlin, Daniel" <dberlin@dberlin.org>
Subject: Re: dataflow branch merging plans.
Date: Tue, 29 May 2007 15:58:00 -0000	[thread overview]
Message-ID: <465C4608.4040903@codesourcery.com> (raw)
In-Reply-To: <465B7BC1.8090208@naturalbridge.com>

Kenneth Zadeck wrote:

>> (1) You will promptly address any regressions introduced by the merge
>> for all targets, provided you get a decent test-case.
>>
>> (2) You will continue to work on integrating the new dataflow machinery
>> into the compiler, to help with the compile-time performance and to help
>> get better results out of the passes that roll their own dataflow stuff.
>>
>> (3) You will promptly fix up coding standards issues that people point out.

> We will continue to work on these issues after the merge. 

Thank you for explicitly confirming that.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

  reply	other threads:[~2007-05-29 15:26 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 [this message]
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
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=465C4608.4040903@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=andrew_pinski@playstation.sony.com \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=bernds_cb1@t-online.de \
    --cc=bonzini@gnu.org \
    --cc=dberlin@dberlin.org \
    --cc=dje@watson.ibm.com \
    --cc=echristo@apple.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=richard.earnshaw@arm.com \
    --cc=seongbae.park@gmail.com \
    --cc=stevenb.gcc@gmail.com \
    --cc=zadeck@naturalbridge.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).