From: Kenneth Zadeck <Kenneth.Zadeck@NaturalBridge.com>
To: gcc-patches@gcc.gnu.org
Cc: Jan Hubicka <jh@suse.cz>
Subject: RE: RTL sharing tester (for testing)
Date: Wed, 27 Jun 2007 15:55:00 -0000 [thread overview]
Message-ID: <87ir99e81j.fsf@moria.site> (raw)
In-Reply-To: <20070626000132.GC995@kam.mff.cuni.cz>
> Hi,
> since dataflow code obviously is making RTL sharing issues worse, I
> tried again the RTL sharing checker patch once again (attached in
> updated form for mainline for everyone who wants to try and hunt down
> some of the issues).
>
> Without any patches I know of only ia-64 to bootstrap with one
> regression in testusite (out of i686, x86-64 and PPC each failing for
> different reasons), so the problem is still quite bad. It seems worse
> than at early stage1 I tried last time despite the numberous sharing
> fixes from dataflow branch, however I hope that number of different
> issues is lesser so we can get it into shape that it does not break the
> common targets used for development and thus can be enabled by default.
>
> With the patch http://gcc.gnu.org/ml/gcc-patches/2007-06/msg01780.html
> I can get i686 and x86-64 into bootstrapland with different 2 testsuite
> regressions, both seems to be caused by regmove pass that is fixable by
> the same infrastructure as introduced by the patch.
>
> Any help with fixing the issues (or reviewing the aforementioned patch
> ;) would be very welcome.
>
> Honza
Honza,
this is a lost cause unless you get permission to actually commit this
patch under stage II and get people to just buy into the grief. You
will never be able to completely catch up, unless people IMMEDIATELY
and ALWAYS see the error of their ways.
What i would suggest in the short term, is for you to hack this patch
so that the checking is only enabled if you configure with some
special --enable-checking option. That at least lowers the cost of
checking and is something that could be checked in with little
controversy.
However, until you get permission to make this patch the default for
--enable-checking, you will be fighting a very labor intensive loosing
battle.
I will say that having chased down too many obscure bugs caused by
sharing, (because as you point out, df is more sensitive to this
problem) I am strongly in favor of this patch.
kenny
next prev parent reply other threads:[~2007-06-27 15:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 3:43 Jan Hubicka
2007-06-27 15:55 ` Kenneth Zadeck [this message]
2007-06-27 18:17 ` Diego Novillo
2007-06-27 21:43 ` Jan Hubicka
2007-06-28 2:02 ` Kaz Kojima
2007-06-28 4:24 ` Jan Hubicka
2007-06-28 8:11 ` Paolo Bonzini
2007-06-28 17:16 ` Kenneth Zadeck
2007-06-28 18:26 ` Jan Hubicka
2007-06-28 19:57 ` Kenneth Zadeck
2007-06-28 20:27 ` Richard Sandiford
2007-06-29 8:29 ` Richard Sandiford
2007-06-29 12:11 ` Kenneth Zadeck
2007-06-29 13:35 ` Paolo Bonzini
2007-06-29 13:37 ` Bernd Schmidt
2007-06-29 13:39 ` Jan Hubicka
2007-06-29 16:55 ` Richard Sandiford
2007-07-13 10:15 ` RFA: Stop df from generating SUBREG REG_NOTES Richard Sandiford
2007-07-25 22:50 ` Richard Sandiford
2007-07-27 0:01 ` Ian Lance Taylor
2007-06-28 20:19 ` RTL sharing tester (for testing) Paolo Bonzini
2007-06-27 23:06 ` Mark Mitchell
2007-06-27 23:06 ` Jan Hubicka
2007-06-27 23:12 ` Eric Christopher
2007-06-28 0:48 ` Jan Hubicka
2007-06-28 22:24 ` Eric Christopher
2007-06-29 23:14 ` Graham Stott
2007-06-30 0:17 ` Jan Hubicka
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=87ir99e81j.fsf@moria.site \
--to=kenneth.zadeck@naturalbridge.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
/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).