From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129704 invoked by alias); 7 Aug 2018 06:27:22 -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 129680 invoked by uid 89); 7 Aug 2018 06:27:21 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=aid, HX-Received:f208, H*r:sk:w10-v6s, HX-Received:sk:m8-v6mr X-HELO: mail-pg1-f178.google.com Received: from mail-pg1-f178.google.com (HELO mail-pg1-f178.google.com) (209.85.215.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 07 Aug 2018 06:27:20 +0000 Received: by mail-pg1-f178.google.com with SMTP id w10-v6so485400pgv.2 for ; Mon, 06 Aug 2018 23:27:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:subject:in-reply-to:cc:from:to:message-id:mime-version :content-transfer-encoding; bh=o3G/Nn0SfHsOU+bguMVvUEHY58bb/Ppo2FyV5puFl1g=; b=GXgGACa1WNLRtoc0enyO8dz7Fl6RSP09lJP02SjSjUg1zliqK0RQ2dFdiraGWk6Fcj zWcbeI2p9zHfkTz0BLEyY2yp+y7PwAC64fQrSueMZiYVrI83MrJck9+Qzgsiv9CmfFII yuX9VrAgVGlC/ACDgjRadOwcOQ/P4uchp02vn6/YaMXgYBKxfigioHqlDfc4qvEL8xZ5 bckH5F5vuJSNnjTIxBA89GVQ1htZAqilAA4WlUrdVoVeR3y/bjXHMSQsn+DI13htefmN Bg/GjSRm2NNuBppxltLz4EyEV9EBdDaRCBiez6LHFgc06RBsCq5XNPu1uGBgEPK8auU+ nTLw== Return-Path: Received: from localhost (c-67-161-15-180.hsd1.ca.comcast.net. [67.161.15.180]) by smtp.gmail.com with ESMTPSA id k64-v6sm778705pgd.47.2018.08.06.23.27.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Aug 2018 23:27:16 -0700 (PDT) Date: Tue, 07 Aug 2018 06:27:00 -0000 X-Google-Original-Date: Mon, 06 Aug 2018 23:15:06 PDT (-0700) Subject: Re: contributing the RISC-V linux native port In-Reply-To: CC: gdb@sourceware.org From: Palmer Dabbelt To: Jim Wilson Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2018-08/txt/msg00017.txt.bz2 On Mon, 06 Aug 2018 19:22:18 PDT (-0700), Jim Wilson wrote: > I'm wondering about what level of functionality I need to reach before > it would be reasonable to try to submit my gdb port. I have a lot of > basic features working, setting breakpoints, run, cont, stepping, > shared libraries, reading/writing int/fp registers, etc, but there are > still a lot of details that need to be worked out for full > functionality. > > My latest testsuite run results are > > === gdb Summary === > > # of expected passes 45195 > # of unexpected failures 1159 > # of unexpected successes 3 > # of expected failures 56 > # of unknown successes 3 > # of known failures 63 > # of unresolved testcases 138 > # of untested testcases 117 > # of unsupported tests 121 > > There are some obvious things broken. 32-bit float values in 64-bit > FP registers aren't printed properly because they are NaN-boxed, and > gdb doesn't know about that yet. I don't have support for signal > handler frames yet. I only have integer register support for core > files. I haven't tried to implement watchpoints yet. There are a lot > of thread failures, 358 in gdb.thread, and apparently some in gdb.mi > also, but there is a glibc patch from Andreas Schwab that I hope fixes > some of them. Most of the rest of the failures I haven't categorized > yet. > > Anyways, I'm wondering how much more work I need to do out of tree > before I can try submitting my work. > > Also, I'm wondering about policy on branches in the gdb tree. Maybe > it would make sense to move my work into a branch in the FSF gdb tree. > I have my own github tree at the moment where I am doing work which is > working fine for me, but it isn't easy for other people to find it. While I'm a RISC-V GDB maintainer, I'm far from active so this doesn't carry much weight. In my opinion (having not looked at the code) I think this is sufficient to bring the port upstream, as if I understand correctly GDB won't release again for six months or so and we should be able to get the major issues cleaned up. Since it looks like most of the actual bugs (as opposed to missing features) cross projects it'd be great to be able to just point everyone to master on the various repos to aid finding the relevant code. Plus, next time I try to debug something I'll probably want to use it and I'm too lazy to find patches unless they're upstream :) Of course, I'll defer to the actual maintainers on this one. Either way, thanks for getting the port in shape!