public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bernds_cb1@t-online.de>
To: Jan Hubicka <jh@suse.cz>,
	  Kenneth Zadeck <Kenneth.Zadeck@NaturalBridge.com>,
	  gcc-patches@gcc.gnu.org, "Bonzini, Paolo" <bonzini@gnu.org>,
	  Kaz Kojima <kkojima@rr.iij4u.or.jp>,
	  zadeck@naturalbridge.com,  rsandifo@nildram.co.uk
Subject: Re: RTL sharing tester (for testing)
Date: Fri, 29 Jun 2007 13:37:00 -0000	[thread overview]
Message-ID: <4684F091.1010904@t-online.de> (raw)
In-Reply-To: <87abujjjnk.fsf@firetop.home>

Richard Sandiford wrote:
> If every register in [regno_first, regno_last] was unused, flow would
> add a REG_UNUSED note for the REG created above.  If only some of those
> registers were unused, flow would add notes for the individual unused
> registers.  As I said on IRC yesterday, I'm not convinced the first
> behaviour was a good idea.  That REG might well be invalid (otherwise
> why have a SUBREG in the first place?) and it's better not to have
> invalid registers floating around.

I agree with everything in your analysis, except possibly this.  If the 
SUBREG is valid, then I see no way how the REG could be invalid.  Since 
flow used to do this, I prefer we keep the same behaviour.


Bernd
-- 
This footer brought to you by insane German lawmakers.
Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 40368
Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif

  parent reply	other threads:[~2007-06-29 11:44 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
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 [this message]
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=4684F091.1010904@t-online.de \
    --to=bernds_cb1@t-online.de \
    --cc=Kenneth.Zadeck@NaturalBridge.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=rsandifo@nildram.co.uk \
    --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).