From: law@redhat.com
To: William Reading <billr@tamu.edu>
Cc: gcc@gnu.org
Subject: Re: Obsolete mn10200?
Date: Mon, 01 Mar 2004 05:12:00 -0000 [thread overview]
Message-ID: <200403010447.i214lbSn014377@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Sun, 29 Feb 2004 20:39:42 CST." <B1899C32-6B29-11D8-876E-000393D95A68@tamu.edu>
In message <B1899C32-6B29-11D8-876E-000393D95A68@tamu.edu>, William Reading wri
tes:
>Howdy,
>
>I was curious as to what would be required to keep this from becoming
>obsoleted.
Basically someone would have to be willing and able to take over maintenance
of the target. That means first bringing it up to current coding standards
then keeping the target working and up-to-standards as those standards change.
The mn102 chip has some special properties that aren't found on many other
chips (for example 24bit wide address registers, and a severe shortage of
registers). As a result it tends to be more susceptible to breakage as the
generic parts of the compiler change -- ie, it tends to be a high maintenance
target.
jeff
prev parent reply other threads:[~2004-03-01 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 2:40 William Reading
2004-03-01 5:12 ` law [this message]
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=200403010447.i214lbSn014377@speedy.slc.redhat.com \
--to=law@redhat.com \
--cc=billr@tamu.edu \
--cc=gcc@gnu.org \
/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).