From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 624 invoked by alias); 7 Oct 2014 00:10:23 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 614 invoked by uid 89); 7 Oct 2014 00:10:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: elasmtp-mealy.atl.sa.earthlink.net Received: from elasmtp-mealy.atl.sa.earthlink.net (HELO elasmtp-mealy.atl.sa.earthlink.net) (209.86.89.69) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 07 Oct 2014 00:10:21 +0000 Received: from [68.104.16.238] (helo=macbook2.local) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1XbIM7-0006BE-Dp for gdb@sourceware.org; Mon, 06 Oct 2014 20:10:19 -0400 Message-ID: <54332F6B.4000409@earthlink.net> Date: Tue, 07 Oct 2014 00:10:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: gdb@sourceware.org Subject: Re: FYI: GCC dropped score support References: <542ECD16.7020907@redhat.com> <20141006233649.GW27467@adacore.com> In-Reply-To: <20141006233649.GW27467@adacore.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da9408d90af9f04d7521538c941f1f61f94b8350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes X-SW-Source: 2014-10/txt/msg00011.txt.bz2 On 10/6/14, 4:36 PM, Joel Brobecker wrote: >> While the deprecation theme is playing in the background ... >> >> I noticed that GCC has just removed support for score: >> >> https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00305.html >> >> I'm looking at score-tdep.c/score-tdep.h and wondering if >> it makes any sense to still maintain that... >> >> http://en.wikipedia.org/wiki/S%2Bcore > > Thinking out loud... > > If the port isn't getting in the way, perhaps we could send out > a quick deprecation warning announce following our standard protocol; > but instead of actually removing support right away, we'd just > keep it on a best-effort basis? I'm not actually sure this is > a good idea at all, as not receiving any response today does not > mean that people might not be starting using it again tomorrow... > > So, unless we think there is enough benefit in remove support for > this target sooner rather than later, the other option is to keep > the info you about GCC in mind if it ever starts getting in the way? > It seems pretty dead, the company's pages are 404, and the only product I can find that used it was the Mattel HyperScan, introduced in 2006 and discontinued in 2008 - apparently it made PC World's "10 Worst Videogames of All Time" list. Even if the code isn't being used, I think it still costs us, in the sense that we have to think about whether it needs changing, it has to be patchedwhen there are global changes, and so forth. So I think we should whack it soon as decently possible. (Of course, the code will actually live on forever, in old releases and repos. :-) ) Stan stan@codesourcery.com