public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
	  "Zadeck, Kenneth" <zadeck@naturalbridge.com>,
	 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: dataflow branch merging plans.
Date: Wed, 23 May 2007 13:19:00 -0000	[thread overview]
Message-ID: <46543F49.8060104@naturalbridge.com> (raw)

I believe that the dataflow branch is now ready to merge into the
mainline.  We have fixed almost all of the performance problems
associated with it.  While there are still some left, we feel
confident that these can be addressed during the rest of stage I and
during stage II.

At this point there is one known correctness regression
(fp-int-convert-float128-timode.c on the x86-64).  This is being
addressed.

I believe we are near or better on generated code on all platforms
than the current trunk.  The only spec performance regressions that we
have seen are tracable to the dataflow branch generating fewer
instructions and you get unlucky sometimes. This has been confirmed by
Vlad in his latest spec runs.

Serge Belyshev has confirmed that the branch builds an runs the x86-64
kernel.  

At this point, we know that the branch works correctly for x86-32,
x86-64, ppc-32, ppc-64 and ia-64 and sh.  We have not recently tested
the arm, spu, mips, z390, and spark.  These did work at some point but
need to be retested to see if any regressions have crept in.

We know there are regressions in the 68k, alpha and the pa-risc.
During the next few days we would like to work on clearing the 68k
regressions.  The alpha port needs attention from someone interested
in maintaining the port.  The pa is abusing regs_ever_live and this
will be addressed after the merge.

When ARM, SPU, Mips, SPARC, and z390 are reconfirmed, approximately
nine ports will work, which is well beyond the criteria approved for
the merge.

While the majority of the hard technical issues have been vetted with
the proper maintainers, most of the patches have not been looked at by
the people who care about the formatting and coding standards (or else
my typing skills have improved dramatically.)  I would invite anyone
who wants to comment on any part of the branch to do so in the next
few days.  You should take a diff with truck revision 124834, the
revision we merged with last Friday.  If you are going to send
comments based on this diff, please make sure to include enough
context to easily find the places that need to be fixed.  This is a
very large patch.

At this point I am closing the branch to improvement except for:
1) comments from above
2) those patches that directly fix regressions or
make more ports work.
3) one patch from Seonbae Park and a few patches from Paolo Bonzini
that are in the queue and will most likely go in today.

I hope to merge this into the truck around the first of next week.  

Thanks everyone for all of the help on this branch.

Kenny

             reply	other threads:[~2007-05-23 13:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 13:19 Kenneth Zadeck [this message]
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
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=46543F49.8060104@naturalbridge.com \
    --to=zadeck@naturalbridge.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=andrew_pinski@playstation.sony.com \
    --cc=belyshev@depni.sinp.msu.ru \
    --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 \
    /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).