From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63230 invoked by alias); 16 Oct 2018 09:42:21 -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 63216 invoked by uid 89); 16 Oct 2018 09:42:21 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.3 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,KAM_SHORT autolearn=ham version=3.3.2 spammy=spring, H*r:sk:gdb@sou, 84, rapidly X-HELO: smtp.CeBiTec.Uni-Bielefeld.DE Received: from smtp.CeBiTec.Uni-Bielefeld.DE (HELO smtp.CeBiTec.Uni-Bielefeld.DE) (129.70.160.84) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 16 Oct 2018 09:42:20 +0000 Received: from localhost (localhost.CeBiTec.Uni-Bielefeld.DE [127.0.0.1]) by smtp.CeBiTec.Uni-Bielefeld.DE (Postfix) with ESMTP id D96C178D for ; Tue, 16 Oct 2018 11:42:17 +0200 (CEST) Received: from smtp.CeBiTec.Uni-Bielefeld.DE ([127.0.0.1]) by localhost (malfoy.CeBiTec.Uni-Bielefeld.DE [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GajDUDwaKa5w for ; Tue, 16 Oct 2018 11:42:16 +0200 (CEST) Received: from lokon.CeBiTec.Uni-Bielefeld.DE (lokon.CeBiTec.Uni-Bielefeld.DE [129.70.161.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.CeBiTec.Uni-Bielefeld.DE (Postfix) with ESMTPS id 7F29378B for ; Tue, 16 Oct 2018 11:42:16 +0200 (CEST) Received: (from ro@localhost) by lokon.CeBiTec.Uni-Bielefeld.DE (8.15.2+Sun/8.15.2/Submit) id w9G9gFbQ007922; Tue, 16 Oct 2018 11:42:15 +0200 (MEST) From: Rainer Orth To: gdb@sourceware.org Subject: Obsoleting Solaris 10 support Date: Tue, 16 Oct 2018 09:42:00 -0000 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (usg-unix-v) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00027.txt.bz2 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. Thanks. Rainer -- ----------------------------------------------------------------------------- Rainer Orth, Center for Biotechnology, Bielefeld University