public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: lars brinkhoff <lars@nocrew.org>
To: Alan Lehotsky <lehotsky@tiac.net>
Cc: gcc@gcc.gnu.org
Subject: Re: PDP-10 backend for gcc
Date: Mon, 28 Aug 2000 23:05:00 -0000	[thread overview]
Message-ID: <853djofvr1.fsf@junk.nocrew.org> (raw)
In-Reply-To: <p04320400b5cc15b2e9eb@[192.168.1.254]>

Alan Lehotsky <lehotsky@tiac.net> writes:
> At 8:05 AM +0200 8/25/00, lars brinkhoff wrote:
> > > On Thu, Aug 24, 2000 at 07:50:09AM +0200, lars brinkhoff wrote:
> > > > I may be writing a PDP-10 backend for gcc during the next year.  It's
> > > > a word-adressed 36-bit machine with a 30-bit virtual address space.
> > Does it seem like it would be possible to write a back end using these
> > pointer formats?
> 
> I've worked on a compiler that supported TWO different sized pointers
> (24 and 32 bits) and there are a lot of problems. [I also worked on
> a compiler for the DEC-10 (Bliss36), so I know a lot about your
> target machine. [If you need someone to bounce ideas off, feel free
> to mail me....]

Thanks!

> The biggest problem you will encounter is the fact that the way that
> RTL is currently generated, you don't really get the opportunity to
> provide any type information about a pointer.  There's basically
> a Pmode that's supposed to be correct for ALL pointers.

So, a hack to make gcc support two pointer formats (global one-word
byte pointers and ordinary global pointers) could be a quick-and-
dirty solution?

> Certainly, if you wanted to sacrifice performance, you could make
> ALL pointers be byte-pointer format (with 36 bit fields) and
> pretty much everything would work.

The problem with this is that one-word global byte pointers can't
point to 36-bit bytes.  (Or so I'm told.)

> Alternatively, you may need to propose an extension to the RTL and 
> the code generator generator so that you can maintain the necessary 
> type information.
> 
> IMHO, such an extension would be a major contribution to the GCC
> community, because these problems keep cropping up in DSP ports
> and the current solutions are less than satisfactory.

I'm quite willing to try this, but I'm not sure that my employer want
to pay for it.

  parent reply	other threads:[~2000-08-28 23:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-23 22:50 lars brinkhoff
2000-08-24  8:36 ` Michael Meissner
2000-08-24 23:43   ` lars brinkhoff
     [not found]     ` <p04320400b5cc15b2e9eb@[192.168.1.254]>
2000-08-28 23:05       ` lars brinkhoff [this message]
2000-08-29  6:57         ` Alan Lehotsky
     [not found]           ` <85vgwkcf28.fsf@junk.nocrew.org>
     [not found]             ` <p04330106b5d17d9f5e1c@[192.168.1.254]>
     [not found]               ` <8566ojn920.fsf@junk.nocrew.org>
     [not found]                 ` <p0433010fb5d1d473ca3a@[192.168.1.254]>
     [not found]                   ` <85itsjkum2.fsf@junk.nocrew.org>
     [not found]                     ` <p04330103b5d2adea14ec@[192.168.1.254]>
2000-08-30  6:45                       ` lars brinkhoff
     [not found]                         ` <p04330104b5d2c3902b09@[192.168.1.254]>
2000-08-30 23:24                           ` lars brinkhoff
2000-08-31 23:09                         ` Jeffrey A Law
2000-09-01  2:16                           ` lars brinkhoff
2000-09-01  2:40                             ` Torbjorn Granlund
2000-09-05 16:05                             ` Michael Meissner
2000-09-05 16:54                               ` Andrew Morton
2000-09-06  2:18                                 ` lars brinkhoff
2000-09-06 15:56                                   ` Michael Meissner
2000-09-06 23:19                                     ` lars brinkhoff
2000-09-06  2:15                               ` lars brinkhoff
2000-09-13  5:17                               ` Nick Ing-Simmons
2000-09-12  4:09 Richard Kenner
2000-09-12  4:10 ` lars brinkhoff
2000-09-12  8:43 ` Michael Meissner

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=853djofvr1.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=gcc@gcc.gnu.org \
    --cc=lehotsky@tiac.net \
    /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).