From: Stan Shebs <shebs@apple.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: deprecate i960 now?
Date: Thu, 03 Oct 2002 11:44:00 -0000 [thread overview]
Message-ID: <3D9C8B8A.9020500@apple.com> (raw)
In-Reply-To: <20021003173232.GA1782@redhat.com>
Richard Henderson wrote:
>It seems that gdb obseleted i960 on 2002-08-22. This makes it
>fairly painful for gcc folk to test on i960, since that killed
>the simulator as well.
>
>I propose that we follow suit and add i960 to the deprecated list
>for 3.3 so that it is removed in 3.4.
>
>Thoughts?
>
You could use Intel's GDB perhaps, since they suggest it in their
massive collection of i960 info at http://www.intel.com/design/i960.
It would be somewhat of a departure to move from obsoleting long-dead
architectures to taking away ones that, in Intel's words (in their
FAQ) are still shipping in "high volumes".
Although I don't have any personal stake in i960 support, I'm a little
troubled by the idea of dropping embedded targets that are still
supported by proprietary compilers. It makes it easy for the
proprietaries to point to the dropping of targets as a reason not
to use GNU for any target, because of the risk of arbitrary decisions
like this. Chucking a never-taped-out oddball like the d30v doesn't
matter, but for a still-used processor like the i960 it really seems
like a retreat.
Stan
next prev parent reply other threads:[~2002-10-03 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 11:32 Richard Henderson
2002-10-03 11:40 ` Mike Stump
2002-10-03 12:13 ` Stan Shebs
2002-10-03 12:19 ` Branko Čibej
2002-10-03 11:44 ` Stan Shebs [this message]
2002-10-03 17:35 ` Joe Buck
2002-10-03 18:48 ` Phil Edwards
2002-10-03 22:32 ` Stan Shebs
2002-10-04 9:55 ` Jim Wilson
2002-10-03 17:37 Robert Dewar
2002-10-04 9:46 ` Jim Wilson
2002-10-04 6:28 Robert Dewar
2002-10-04 11:30 ` Richard Henderson
2002-10-05 5:56 Robert Dewar
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=3D9C8B8A.9020500@apple.com \
--to=shebs@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).