public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: lars brinkhoff <lars@nocrew.org>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org, Joe Buck <jbuck@racerx.synopsys.com>,
	Mark Mitchell <mark@codesourcery.com>,
	meissner@cygnus.com
Subject: Re: PDP10 support
Date: Thu, 14 Sep 2000 00:15:00 -0000	[thread overview]
Message-ID: <85n1hbfnq5.fsf@junk.nocrew.org> (raw)
In-Reply-To: <Pine.BSF.4.21.0009132337510.23043-100000@deneb.dbai.tuwien.ac.at>

Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
> FWIW, that makes three global write commiters/four SC members that view
> your proposal as useful in principle, if I've counted correctly. ;-)

These are the positive comments I've found, with Mark Mitchell being
the most sceptical, and almost everyone pointing out that PDP-10
support is quite useless in itself.

It would also be interesting to hear from the DSP folks.

Michael Meissner <meissner@cygnus.com> writes:
> On Wed, Sep 06, 2000 at 11:18:00AM +0200, lars brinkhoff wrote:
> > Isn't it about time gcc was enhanced to support "weird" pointers?
> Sure I do.

Mark Mitchell:
> Those kind of generic changes are probably welcome -- especially if
> they don't add much maintenance overhead, and if there are other
> architectures that have similarly unusual pointer formats.

kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
> [...] adding support for this, if done cleanly, is likely to
> be a worthwhile addition to GCC since it may produce a level of
> abstraction in the handling of pointers that might make *other*
> things easlier down the road.

Jeffrey A Law <law@cygnus.com> writes:
> [...] changes which improve GCC's handling of multiple pointer
> formats are of interest to us as there are modern targets which
> would benefit from that infrastructure.

Joe Buck <jbuck@racerx.synopsys.com> writes:
> [...] there's a large group of word-oriented architectures out there
> (DSPs).  [...]  For that reason, your work may be interesting.
> [...] I have a vague feeling that the quality of the back end may be
> improved and possibly more opportunities for improvement exposed if
> careful attention is paid to what is an address and what is an
> integer, as this work will require.

Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
> On Tue, 12 Sep 2000, Joe Buck wrote:
> > [...] For that reason, your work may be interesting.
> Seconded.

  reply	other threads:[~2000-09-14  0:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-09 12:33 m68k MacOS target support? Michael Sokolov
2000-09-11 20:47 ` Stan Shebs
2000-09-11 20:56   ` Michael Meissner
2000-09-11 21:33     ` Mark Mitchell
2000-09-12  0:02       ` lars brinkhoff
2000-09-12  0:15         ` Mark Mitchell
2000-09-12  3:26           ` lars brinkhoff
2000-09-12  7:23             ` Mark Mitchell
2000-09-12 11:16           ` Joe Buck
2000-09-12 11:22             ` Bernd Schmidt
2000-09-12 20:11               ` Mark Mitchell
2000-09-12 13:59             ` Stan Shebs
2000-09-12 17:55               ` Richard Henderson
2000-09-12 19:12                 ` Stan Shebs
2000-09-12 22:44                 ` "Dead" Ports (was: m68k MacOS target support?) Gerald Pfeifer
2000-09-13  9:26                   ` Jeffrey A Law
2000-09-13  9:33                     ` Bernd Schmidt
2000-09-13 11:40                       ` Stan Shebs
2000-09-13  9:57                     ` Bruce Korb
2000-09-13  3:17                 ` m68k MacOS target support? Joseph S. Myers
2000-09-12 11:48           ` Toon Moene
2000-09-12  7:32         ` Jeffrey A Law
2000-09-12 11:11         ` PDP10 support (was Re: m68k MacOS target support?) Joe Buck
2000-09-13 14:51           ` PDP10 support Gerald Pfeifer
2000-09-14  0:15             ` lars brinkhoff [this message]
2000-09-14  7:47               ` Nick Ing-Simmons
2000-09-12  0:03       ` m68k MacOS target support? lars brinkhoff
2000-09-12  9:52   ` David Huggins-Daines

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=85n1hbfnq5.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@racerx.synopsys.com \
    --cc=mark@codesourcery.com \
    --cc=meissner@cygnus.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).