From: Jeffrey A Law <law@cygnus.com>
To: "Michael P. Hayes" <michaelh@ongaonga.chch.cri.nz>
Cc: Joern Rennecke <amylaar@cygnus.co.uk>, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: Autoincrement addressing modes
Date: Wed, 11 Feb 1998 18:20:00 -0000 [thread overview]
Message-ID: <20650.887245518@hurl.cygnus.com> (raw)
In-Reply-To: <199802120014.NAA29645@ongaonga.chch.cri.nz>
In message < 199802120014.NAA29645@ongaonga.chch.cri.nz >you write:
> > The PA has similar constraints.
>
> Does this asymmetry only apply to these update forms of addressing
> modes?
Well, there's some weird asymmetry problems with nearly all of the addressing
modes, except for (reg) on the PA. Many we are able to ignore, others we
deal with by not considering such addresses valid according to
GO_IF_LEGITIMATE_ADDRESS -- we do allow them in some predicates when we
can check for the weird problems.
> Any ideas how to describe this to GCC? I suppose if there was a flag
> to differentiate memory reads from writes, then
> GO_IF_LEGITIMATE_ADDRESS could reject the invalid forms.
So far we haven't tried.
Being able to distinguish between loads & stores in GO_IF_LEG... would be
a big step forward, but a lot of work.
My recommendation would be to not try and handle *all* the cases in the
first submission. Just get something that can be extended, particularly
if we do fix GO_IF_LEG... later.
jeff
next prev parent reply other threads:[~1998-02-11 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-11 18:20 Michael P. Hayes
1998-02-11 16:33 ` Joern Rennecke
1998-02-11 17:22 ` Jeffrey A Law
1998-02-11 17:22 ` Michael P. Hayes
1998-02-11 16:33 ` Joern Rennecke
1998-02-11 18:20 ` Joern Rennecke
1998-02-11 18:20 ` Jeffrey A Law [this message]
1998-02-12 6:42 ` Richard Henderson
1998-02-14 15:24 ` Michael P. Hayes
1998-03-16 20:25 ` Joern Rennecke
1998-03-16 20:25 ` Richard Henderson
1998-03-16 20:25 ` Michael P. Hayes
1998-03-16 20:25 ` Joern Rennecke
1998-03-17 1:28 ` Richard Henderson
1998-03-17 13:29 ` Joern Rennecke
1998-03-16 20:44 ` Michael P. Hayes
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=20650.887245518@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=michaelh@ongaonga.chch.cri.nz \
/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).