From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28009 invoked by alias); 30 Jun 2010 02:00:36 -0000 Received: (qmail 27960 invoked by uid 22791); 30 Jun 2010 02:00:35 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mail-vw0-f47.google.com (HELO mail-vw0-f47.google.com) (209.85.212.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 30 Jun 2010 02:00:30 +0000 Received: by vws12 with SMTP id 12so359686vws.20 for ; Tue, 29 Jun 2010 19:00:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.191.68 with SMTP id dl4mr4512247qcb.159.1277863228253; Tue, 29 Jun 2010 19:00:28 -0700 (PDT) Received: by 10.229.190.136 with HTTP; Tue, 29 Jun 2010 19:00:28 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Jun 2010 09:51:00 -0000 Message-ID: Subject: Re: Power/PowerPC RIOS/RIOS2 obsolescence From: David Edelsohn To: Kevin Bowling Cc: gcc@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-06/txt/msg00862.txt.bz2 On Tue, Jun 29, 2010 at 7:07 PM, Kevin Bowling w= rote: > My argument is simply this, sorry if it wasn't clear in the last > email, bottom line up front: > - It can just as easily be removed in the future if it is broken for > more than one release rather than evicting support. > - It shouldn't add unwieldy maintenance overhead. =A0The old stuff can > be walled off, conditionally built, and otherwise removed from the > main focus. > - The code is already written and just needs a maintainer. > - I have the hardware and desire to maintain it. > > Please reread the last paragraph in my previous email. =A0The CPU > architecture is still manufactured and in use. =A0This is a strawman > argument as I cannot say that these organizations are using GCC but it > wouldn't be unimaginable. RAD6000 has been superceded by RAD750. No RIOS hardware is manufactured nor used. RAD6000 *was* manufactured. RAD750 is manufactured. And any developers still using RAD6000 would not program the hardware with GCC 4.6. Despite your assertions, it is a significant maintenance overhead for some of the improvements that we want to add to the rs6000 port. It literally doubles the amount of changes to modify all of the POWER architecture machine description patterns. The problem is not a lack of maintainer. I have been maintaining the code for almost 20 years. If you need RIOS support in GCC 4.6, you can re-introduce the removed code in your private tree. David