From: Richard Henderson <rth@redhat.com>
To: law@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: paradoxical subreg problem
Date: Mon, 28 Jan 2002 13:18:00 -0000 [thread overview]
Message-ID: <20020128121508.A26102@redhat.com> (raw)
In-Reply-To: <16912.1012248200@porcupine.cygnus.com>; from law@redhat.com on Mon, Jan 28, 2002 at 01:03:20PM -0700
On Mon, Jan 28, 2002 at 01:03:20PM -0700, law@redhat.com wrote:
> However, even if we do that I think we need to clarify precisely what
> the semantics of a paradoxical subreg really are. Clearly there is
> some confusion.
With plain registers, I don't think there is any confusion -- the
upper bits are simply undefined. With memories, there is confusion.
But I think we should "clarify" by disallowing them.
> [ Actually my preference would be to zap paradoxical subregs, but I
> don't think we're in a position to do that right now. ]
Nope.
r~
next prev parent reply other threads:[~2002-01-28 20:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 11:36 law
2002-01-28 11:50 ` Richard Henderson
2002-01-28 11:58 ` law
2002-01-28 12:05 ` Richard Henderson
2002-01-28 12:09 ` law
2002-01-28 12:39 ` Richard Henderson
2002-01-28 13:03 ` law
2002-01-28 13:18 ` Richard Henderson [this message]
2002-01-28 14:25 ` Michael Matz
2002-01-28 12:15 ` Michael Matz
2002-01-28 15:41 ` Jim Wilson
2002-01-29 1:57 ` Jim Wilson
2002-01-29 10:55 ` Richard Earnshaw
2002-01-29 12:21 ` paradoxical subreg problem [ patch attached ] law
2002-01-29 13:46 ` Richard Earnshaw
2002-01-29 16:41 ` Jim Wilson
2002-01-29 18:08 ` law
2002-01-31 13:22 ` law
2002-01-28 12:03 paradoxical subreg problem Richard Kenner
2002-01-28 12:15 ` law
2002-01-28 12:18 Richard Kenner
2002-01-28 12:47 ` law
2002-01-28 14:53 ` law
2002-01-29 10:31 ` Richard Earnshaw
2002-01-28 12:47 Richard Kenner
2002-01-28 13:10 ` law
2002-01-28 13:25 Richard Kenner
2002-01-28 13:46 ` David Edelsohn
2002-01-28 15:20 ` law
2002-01-28 15:50 ` Geoff Keating
2002-01-28 15:21 Richard Kenner
2002-01-28 15:41 ` law
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=20020128121508.A26102@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.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).