From: Matthew Wilcox <willy@debian.org>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: willy@debian.org, gcc@gcc.gnu.org
Subject: Re: PA specifies invalid T_ADAFLAGS
Date: Fri, 26 Apr 2002 08:11:00 -0000 [thread overview]
Message-ID: <20020426153648.B24907@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <10204260954.AA16645@vlsi1.ultra.nyu.edu>; from kenner@vlsi1.ultra.nyu.edu on Fri, Apr 26, 2002 at 05:54:24AM -0400
On Fri, Apr 26, 2002 at 05:54:24AM -0400, Richard Kenner wrote:
> I think you're slightly confused. Unless you modify the gcc backend,
> it's just not possible to output instructions which use sr0-3.
>
> Sure it is, if you have a large enough virtual origin.
No, it really isn't. See
http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,959!26!244,00.html
Only space registers 4-7 are used for implicit addressing. gcc doesn't
do explicit addressing.
Are you perhaps confused with ia64 where the address space is divided
into 8 rather than 4?
--
Revolutions do not require corporate support.
next parent reply other threads:[~2002-04-26 14:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10204260954.AA16645@vlsi1.ultra.nyu.edu>
2002-04-26 8:11 ` Matthew Wilcox [this message]
2002-04-26 16:14 Robert Dewar
-- strict thread matches above, loose matches on Subject: below --
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 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
2002-04-25 2:47 ` Olivier Hainque
2002-04-25 2:58 ` Michael Matz
2002-04-25 9:25 ` 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=20020426153648.B24907@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).