* Obsolete mn10200?
@ 2004-03-01 2:40 William Reading
2004-03-01 5:12 ` law
0 siblings, 1 reply; 2+ messages in thread
From: William Reading @ 2004-03-01 2:40 UTC (permalink / raw)
To: gcc
Howdy,
I was curious as to what would be required to keep this from becoming
obsoleted.
Regards,
William Reading
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Obsolete mn10200?
2004-03-01 2:40 Obsolete mn10200? William Reading
@ 2004-03-01 5:12 ` law
0 siblings, 0 replies; 2+ messages in thread
From: law @ 2004-03-01 5:12 UTC (permalink / raw)
To: William Reading; +Cc: gcc
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-03-01 5:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-01 2:40 Obsolete mn10200? William Reading
2004-03-01 5:12 ` law
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).