From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Bernd Schmidt <bernds_cb1@t-online.de>
Cc: Kenneth Zadeck <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>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: dataflow branch merging plans.
Date: Fri, 25 May 2007 10:32:00 -0000 [thread overview]
Message-ID: <4656B24E.9080800@lu.unisi.ch> (raw)
In-Reply-To: <4656AFFD.1040605@t-online.de>
> Still, 6% compile time regression on several targets and typically a
> (very small) regression in SPEC scores - am I the only one who's not
> impressed?
I must say, I am not either despite the (not so big, but relevant) work
I put in the branch. I'm not sure whether this includes or not the
dataflow checking code; this is way too expensive and it should be
relocated to a separate --enable-checking=df option when we're closer to
the release.
(Actually, I was supposed to do it in April, but I was swamped and --
anyway -- yesterday's spu bug convinced me that it is better to leave it
in for a while).
One important thing is that this is also an enabling work for other
improvements. I remember Kenny had prespilling, but it didn't work
because of the wrong liveness computation (it worked right on
df-branch instead).
> Finally, since a plan to merge next week was indicated - which
> maintainer has approved it?
I think the message was also meant to find a maintainer approving it.
Paolo
next prev parent reply other threads:[~2007-05-25 9: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 [this message]
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=4656B24E.9080800@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--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).