From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 6ZJULHGG01/CZgAAWB0awg (envelope-from ) for ; Fri, 11 Dec 2020 09:47:13 -0500 Received: by simark.ca (Postfix, from userid 112) id 8FC311F0A9; Fri, 11 Dec 2020 09:47:13 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (unknown [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 270151E552 for ; Fri, 11 Dec 2020 09:47:13 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 88C3E385480A; Fri, 11 Dec 2020 14:47:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 88C3E385480A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1607698032; bh=ZamZyGPdLXY91F9RIkP/XtnQGae8R3fiFmeP4X0aI0o=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=KqaEo4aPk8i8hxrKs+ZLtYShr+ZxuTjgJ4lAFA6SFloQbM5HQ8IYvlJ+33ULW6phs b6M5hdtPPIXapIVlUEQhqRINXtXwfqFOEiPZ82RFwsngQQIiZvaDaseQz0eldKcn1g a5Br+yqcmFb+zK9GJuNBFr6yjAjSUzYiC9cOStkM= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 123A8385480A for ; Fri, 11 Dec 2020 14:47:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 123A8385480A Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 0BBEl443022875 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 11 Dec 2020 09:47:09 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 0BBEl443022875 Received: from [10.0.0.11] (173-246-6-90.qc.cable.ebox.net [173.246.6.90]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 7F59D1E552 for ; Fri, 11 Dec 2020 09:47:04 -0500 (EST) To: "gdb@sourceware.org" Subject: Proposal to Removal of QNX Neutrino support from GDB Message-ID: <4205d383-e98e-f591-9031-f48925634c65@polymtl.ca> Date: Fri, 11 Dec 2020 09:47:04 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Fri, 11 Dec 2020 14:47:04 +0000 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb Reply-To: Simon Marchi Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" Hi, Given that: - there hasn't been contributions to the QNX Neutrino port for a while [1] - there is no maintainer for it - the tools to build and run QNX programs are not publicly available for anybody to test this support I propose to remove QNX Neutrino support from GDB for GDB 12. That means the support would still be included in GDB 11, the next release, and removed just after the GDB 11 branch is created. There are two parts to it: 1. Native bits for when GDB itself runs on Neutrino (nto-procfs.c) 2. Neutrino target support (nto-tdep.c and friends) We can't compile #1, as that requires the Neutrino SDK. We can build-test #2, as it doesn't require Neutrino-specific include files, but we can't run it. The current plan is to remove both. But if Neutrino target support (#2) is still being used (say, with a custom remote target), but native support (#1) isn't, one option is to only remove the native bits, so we only keep the part that anybody can at least build. If somebody would like the support for Neutrino to stay in GDB, please speak up. If so, we will need a maintainer to step up and become responsible to that port. There is a patch series that implement the proposal here: https://sourceware.org/pipermail/gdb-patches/2020-December/173894.html Thanks, Simon [1] Last one was d7161de46af ("[nto] Improve ABI sniffing.")