From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76257 invoked by alias); 16 Oct 2018 14:20:31 -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 76148 invoked by uid 89); 16 Oct 2018 14:20:30 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Joel, stand X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 16 Oct 2018 14:20:28 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0BBD456010; Tue, 16 Oct 2018 10:20:27 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YN6A41-aziJx; Tue, 16 Oct 2018 10:20:26 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id D589556004; Tue, 16 Oct 2018 10:20:26 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 924F1889F1; Tue, 16 Oct 2018 07:20:24 -0700 (PDT) Date: Tue, 16 Oct 2018 14:20:00 -0000 From: Joel Brobecker To: Rainer Orth Cc: gdb@sourceware.org Subject: Re: Obsoleting Solaris 10 support Message-ID: <20181016142024.GD17534@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-SW-Source: 2018-10/txt/msg00028.txt.bz2 Hi Rainer, > Yesterday I've announced the obsoletion of Solaris 10 support in GCC 9 > > https://gcc.gnu.org/ml/gcc/2018-10/msg00139.html > > I believe the same reasons cited there hold for GDB as well. Besides, > we had some build failures recently that only occured on Solaris 10, > creating work to support a rapidly dwindling or even vanished user base. > Therefore, I wonder how best to handle this in GDB. > > While GCC has roughly one release a year and GCC 9, the last relase to > support Solaris 10 with --enable-obsolete, will appear sometime next > spring, GDB has a release cycle of about 6 months. Should we obsolete > Solaris 10 for GDB 8.3 now, getting a bit ahead of GCC, or rather wait > for GDB 8.4 instead? My gut feeling is that it would be better to wait > for 8.4: more often than not GCC adds support for new DWARF versions or > other extensions, and it would be good to have a GDB that supports > what's in the GCC 9 release. I don't know of any particular issue that might create a strong reason for dropping Solaris 10 support in the short term; and I agree that it would be nice for the users on Solaris 10 to continue providing newer versions of GDB on that platform until GCC also stops. However, this is only really possible if contributors like yourself stand behind it. So, in my mind, I would continue with the default stand where we keep support by default as long as it doesn't unduly slows the rest of GDB development. -- Joel