From: law@redhat.com
To: Richard Henderson <rth@redhat.com>
Cc: Arnaud Charlet <charlet@ACT-Europe.FR>,
John David Anglin <dave@hiauly1.hia.nrc.ca>,
Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
gcc@gcc.gnu.org
Subject: Re: PA specifies invalid T_ADAFLAGS
Date: Fri, 26 Apr 2002 10:51:00 -0000 [thread overview]
Message-ID: <12820.1019841420@porcupine.cygnus.com> (raw)
In-Reply-To: Your message of Thu, 25 Apr 2002 00:48:56 PDT. <20020425004856.B2022@redhat.com>
In message <20020425004856.B2022@redhat.com>, Richard Henderson writes:
> On Thu, Apr 25, 2002 at 09:08:09AM +0200, Arnaud Charlet wrote:
> > It sure has. This patch is pretty old at this stage. The situation has bee
> n
> > reviewed very recently.
>
> I've read this whole thread and, like John and Matt, I *still* don't
> know exactly the problem you and Robert are referring to.
>
> I think yall should supply a failing test case rather than continue
> to say "it doesn't work". At minimum this properly documents the
> problem.
Conceptually you're allows to have a pointer outside the object it points to;
dereferences of the pointer will include an offset which will bring the
resulting address back into the original object. This really mucks up the
implicit space register selection on the PA -- space registers are implicitly
selected by the upper 2 bits of the base register (not the effective address!).
I can't remember how to do much of anything in data, but if you wanted to
dig further, you'd want to look for something like "virtual origins" in the
Ada spec.
jeff
next prev parent reply other threads:[~2002-04-26 17:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 19:59 Richard Kenner
2002-04-24 22:07 ` John David Anglin
2002-04-25 0:18 ` Arnaud Charlet
2002-04-25 0:49 ` Richard Henderson
2002-04-26 10:51 ` law [this message]
2002-04-25 2:47 ` Olivier Hainque
2002-04-25 2:58 ` Michael Matz
2002-04-25 9:25 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 16:14 Robert Dewar
[not found] <10204260954.AA16645@vlsi1.ultra.nyu.edu>
2002-04-26 8:11 ` Matthew Wilcox
2002-04-26 4:06 Richard Kenner
2002-04-25 22:55 Matthew Wilcox
2002-04-25 21:14 Robert Dewar
2002-04-25 20:52 Robert Dewar
2002-04-25 21:53 ` John David Anglin
2002-04-25 19:58 Robert Dewar
2002-04-25 20:51 ` John David Anglin
2002-04-25 19:45 Robert Dewar
2002-04-25 19:37 Robert Dewar
2002-04-25 19:55 ` John David Anglin
2002-04-25 5:35 Richard Kenner
2002-04-26 10:54 ` law
2002-04-25 3:37 Richard Kenner
2002-04-24 22:08 Robert Dewar
2002-04-24 21:27 Robert Dewar
2002-04-24 20:37 Robert Dewar
2002-04-24 20:44 ` Matthew Wilcox
2002-04-24 21:44 ` John David Anglin
2002-04-24 20:09 Robert Dewar
2002-04-24 20:06 Robert Dewar
2002-04-24 20:26 ` Matthew Wilcox
2002-04-24 21:39 ` John David Anglin
2002-04-24 12:07 John David Anglin
2002-04-24 12:43 ` Matthew Wilcox
2002-04-25 15:04 ` John David Anglin
2002-04-26 10:56 ` law
2002-04-26 11:28 ` John David Anglin
2002-04-24 13:27 ` Arnaud Charlet
2002-04-24 13:38 ` John David Anglin
2002-04-24 14:28 ` Arnaud Charlet
2002-04-24 22:47 ` John David Anglin
2002-04-26 9:35 ` law
2002-04-26 9:39 ` John David Anglin
2002-04-26 10:43 ` law
2002-04-24 10:27 Matthew Wilcox
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=12820.1019841420@porcupine.cygnus.com \
--to=law@redhat.com \
--cc=charlet@ACT-Europe.FR \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=rth@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).