From: Doug Evans <dje@transmeta.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: David Taylor <taylor@cygnus.com>,
Kevin Buettner <kevinb@cygnus.com>, Nick Duffek <nsd@cygnus.com>,
Michael Snyder <msnyder@cygnus.com>, Jim Blandy <jimb@cygnus.com>,
GDB Discussion <gdb@sources.redhat.com>
Subject: Re: harvard architectures - the d10v
Date: Thu, 08 Feb 2001 23:59:00 -0000 [thread overview]
Message-ID: <14979.41818.127484.943746@casey.transmeta.com> (raw)
In-Reply-To: <3A831746.CAB9C621@cygnus.com>
Andrew Cagney writes:
> Doug Evans wrote:
>
> > > ``But the d10v is a hack''? So? The point of the d10v, wasn't to
> > > provide a reference implementation (anything but!) but rather to provide
> > > a vehicle through which a reference implementation could be developed.
> >
> > I don't know that the d10v was all the good a reference implementation
> > or that one is even needed for the task at hand.
>
> Notice that I carefully avoided calling the d10v a reference
> implementation. It isn't and I'm not claiming that it is. Rather it is
> a working example. The moment anyone refers to the D10V code they are
> probably missing the point :-)
I don't want to get into a debate over the pedantically correct
definition of a reference implementation. And since you're the
one who brought the d10v up, I wonder who's the one missing the point. :-)
> The thing to do with the d10v is look at how the user is able to
> interact with it. For instance, the user can cut addresses from one
> part of the screen and paste them directly into new commands. The user
> can use 0 and have it mean NULL. It is that sort of subtlety that the
> d10v managed to resolve.
There may yet be subtleties involved, but I wouldn't put those
in that category.
> The one thing people shouldn't be doing is designing some new set of
> implementations without looking at what has been before and seeing how
> real people felt things should work.
I'm with Per. There's some infrastructure that's a prerequisite.
next prev parent reply other threads:[~2001-02-08 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 11:52 Andrew Cagney
[not found] ` <14979.2615.608456.807316@casey.transmeta.com>
[not found] ` <3A831746.CAB9C621@cygnus.com>
2001-02-08 23:59 ` Doug Evans [this message]
[not found] <200102082037.PAA07784@texas.cygnus.com>
[not found] ` <14979.4102.901998.291182@casey.transmeta.com>
2001-02-09 0:25 ` Eli Zaretskii
2001-02-09 7:32 David Taylor
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=14979.41818.127484.943746@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@cygnus.com \
--cc=kevinb@cygnus.com \
--cc=msnyder@cygnus.com \
--cc=nsd@cygnus.com \
--cc=taylor@cygnus.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