From: Diego Novillo <dnovillo@google.com>
To: Jan Hubicka <jh@suse.cz>
Cc: gcc-patches@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re: RTL sharing tester (for testing)
Date: Wed, 27 Jun 2007 18:17:00 -0000 [thread overview]
Message-ID: <468283E0.3010004@google.com> (raw)
In-Reply-To: <20070626000132.GC995@kam.mff.cuni.cz>
On 6/25/07 8:01 PM, Jan Hubicka wrote:
> 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.
How expensive is this verification? My inclination is to enable the
sharing verifier in a couple of steps:
1- Right now, enable it in every pass that doesn't expose bootstrap
problems. I'm actually willing to live with breakage in the testsuite
and address it during stages 2 and 3.
2- Once the bootstrap problems are fixed, leave the verifier enabled
everywhere.
But since this will affect stages 2 and 3, I'd like to get Mark's opinion.
next prev parent reply other threads:[~2007-06-27 15:36 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
2007-06-27 18:17 ` Diego Novillo [this message]
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=468283E0.3010004@google.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=mark@codesourcery.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).