From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 49681 invoked by alias); 16 Oct 2019 13:21:02 -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 49673 invoked by uid 89); 16 Oct 2019 13:21:02 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=H*f:sk:CAFyWVa, H*i:sk:CAFyWVa, Wilson X-HELO: esa4.hgst.iphmx.com Received: from esa4.hgst.iphmx.com (HELO esa4.hgst.iphmx.com) (216.71.154.42) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 16 Oct 2019 13:21:01 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wdc.com; i=@wdc.com; q=dns/txt; s=dkim.wdc.com; t=1571232061; x=1602768061; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=yvGrP2E9w5Z+Ij2ZH2Q9ufWZZXQ/vghJ7RlmlE4dmMQ=; b=mx62rejgNm6yJjwWzpw+7HFlB2fuGbR60GnJNWm7zisAZgLTDTKuCMxq tqwo9HoILFKgE/dIpVhuUTFu88si6iybbvkrAaqaeNPNaGUI0QYd+OeRL lPP2IMKOvZeCTTnwC2DsLwA5yeOoGgvgn3YI0S5mYMHUAOeOz9k6MC77c Ljfwhn+OKLN3B9ytf1mO5z1RvIfN/q7jwglPBbR8Yf0F/I4JRLEcg8VqE 2WRRJH8z90OkgnXuCnXLMzSmpjc+DyiUzJvyf2GUe9X3863aFRSWniVki leXRypWWEu4BIicRiPFyAmuEvpDijKG/lIKIXAoRV4yoz3LVCGtuiiRKL Q==; IronPort-SDR: y5fV6aZzR58gDF5YU3V1G8ycv//B3elyhR3dyetJzcT9MXnC7nIqavZNCQ18LxC5TnFBFvv7KR cQdWaBpVHj3252Mx/YBNFJnl/3tmDIojMtNygO0BNWCL4h1giAD+zd/4Cue0D6TTblGjhFCXj3 RVRNG3XUkRF4O9M3pPFy6kMFC+7g029+QPnHt8nK+79cbegkhw64DpYIPYR74YbI+H3cxiS9VX lS9OX8CLpjswVjZDI9qvy8RGbkrsOb6odp3ZjJxpjpFi3J9XyjCBAerjwo9VybjQk9dNn0t2DA bs4= Received: from h199-255-45-15.hgst.com (HELO uls-op-cesaep02.wdc.com) ([199.255.45.15]) by ob1.hgst.iphmx.com with ESMTP; 16 Oct 2019 21:20:59 +0800 IronPort-SDR: U2xhBWXc/Nd20WGA8zonHx/7EqSbH046IlwJEuRc/xgmXJiPZjs0CAdzoGYO16k2OZ0nFr1OFp DT22Ir79VUsTkFDkc6C1Ota+ais9hrfKDSnpkQXG1tG+esa/fjkpAKnP0xGBeu21/5wHrxPD2X XN6oVUCokSQlpgqbm0NXuSiXjbzecK38/lj/HElOazUb8PgwsriW+wueOZOFVk5eV5Sl1XDD1E IlCqSl5Vx/eJt6usiAg4RyKdRVm8GPrOd1z8RIHdTjI/ITvO5J5Ei1Hx11kEuugBAHLZXW+QFj lTpkZeCB7iuj1uLkbe/hgBbo Received: from uls-op-cesaip01.wdc.com ([10.248.3.36]) by uls-op-cesaep02.wdc.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Oct 2019 06:16:47 -0700 IronPort-SDR: nS6gGs0uoXnjRFIPRhDcm3Bi3NKgjRmJZhQVqNQHXOVicmeZUZ+GGY9evV1cWbcr2T+Ec5BKI/ 02v9h2sIsvmhVhY5dlR5VXUKYRwUTzeZgewwU3WVYATTYR1UyfZd096g3AWW2DIYyFuWM2HQBJ H8nSvGtDbvKhKVt2Y7Yyu1S9aB4NhvixCHN9uEnvKpGMZNR6/l1qeYtZG/XOeAU6XfWkUpi7Oq bDdMpDCDkiXtcQqyhpTt6MmCvxX1QCNwuG2w4KcuCxveZL+XSdSsvcFQpdwtGe7Q27zdMrA0iC +Qs= WDCIronportException: Internal Received: from unknown (HELO redsun52) ([10.149.66.28]) by uls-op-cesaip01.wdc.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Oct 2019 06:20:59 -0700 Date: Wed, 16 Oct 2019 13:21:00 -0000 From: "Maciej W. Rozycki" To: Jim Wilson cc: Vincent Chen , gdb@sourceware.org, Paul Walmsley Subject: Re: RISC-V: Is it reasonable to extend current target_description for KGDB? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (LFD 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-SW-Source: 2019-10/txt/msg00014.txt.bz2 On Tue, 15 Oct 2019, Jim Wilson wrote: > One possible solution is to add a RISC-V specific command to choose > the register set used for the default p packet. That way, if there > are problems with adding registers to it, people have the option to > switch back to the old way. We already have the "set riscv > use-compressed-breakpoints [auto|on|off]" command. So we could add a > similar command to choose the number of registers in the default p > packet, try changing the default to the full 36 register set, and wait > to see who complains. People that complain can be told about the > command to switch back to the old 32 (33?) register set. There's such a generic command already available: (gdb) set tdesc filename ... NB, this has nothing to do with the use of `g'/`G' vs `p'/`P' packets, both use the same register indices; for the overlapping part, that is of course. Then no heuristics can cover registers outside the range of the `g'/`G' packets of course, an XML description does have to be provided for those registers to be recognised. Maciej