From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31126 invoked by alias); 1 Mar 2004 05:12:03 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 31119 invoked from network); 1 Mar 2004 05:12:03 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sources.redhat.com with SMTP; 1 Mar 2004 05:12:03 -0000 Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.24) id 1AxfhH-00080v-4p for gcc@gnu.org; Mon, 01 Mar 2004 00:10:31 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1Axfhs-0000Hf-H3 for gcc@gnu.org; Mon, 01 Mar 2004 00:11:40 -0500 Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.30) id 1Axfhs-0000Gg-66 for gcc@gnu.org; Mon, 01 Mar 2004 00:11:08 -0500 Received: from [66.187.233.31] (helo=mx1.redhat.com) by mx20.gnu.org with esmtp (Exim 4.30) id 1AxfLL-0004oy-Lf for gcc@gnu.org; Sun, 29 Feb 2004 23:47:51 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id i214leb30584; Sun, 29 Feb 2004 23:47:40 -0500 Received: from speedy.slc.redhat.com (vpn50-43.rdu.redhat.com [172.16.50.43]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i214ld814100; Sun, 29 Feb 2004 23:47:39 -0500 Received: from redhat.com (law@localhost) by speedy.slc.redhat.com (8.12.10/8.12.8/Submit) with ESMTP id i214lbSn014377; Sun, 29 Feb 2004 21:47:37 -0700 Message-Id: <200403010447.i214lbSn014377@speedy.slc.redhat.com> X-Authentication-Warning: speedy.slc.redhat.com: law owned process doing -bs To: William Reading cc: gcc@gnu.org Reply-To: law@redhat.com Subject: Re: Obsolete mn10200? In-Reply-To: Your message of "Sun, 29 Feb 2004 20:39:42 CST." From: law@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Mar 2004 05:12:00 -0000 X-Spam-Status: No, hits=-0.1 required=5.0 tests=IN_REP_TO,NO_REAL_NAME,X_AUTH_WARNING version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-SW-Source: 2004-03/txt/msg00031.txt.bz2 In message , 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