From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130250 invoked by alias); 7 Aug 2018 02:22:23 -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 129463 invoked by uid 89); 7 Aug 2018 02:22:22 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=submitting X-HELO: mail-wm0-f43.google.com Received: from mail-wm0-f43.google.com (HELO mail-wm0-f43.google.com) (74.125.82.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 07 Aug 2018 02:22:21 +0000 Received: by mail-wm0-f43.google.com with SMTP id y9-v6so16351057wma.5 for ; Mon, 06 Aug 2018 19:22:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=GYXtxoDUGsoXshGwBXIHXvgejkOif+zT/FBCdopA5JI=; b=UfoUUqcbreBJhvKgHw1eat571gbtds4Th9WaM/RBqBi+29SA+26/3q5nmdnkaC4kwH PlgVElVzL6/u+wf/mz3D213PEezXiodVQMz2b/DFsd1BctXcO5sDBhBvJZwd27UWwjOc li5xSuuB9AALMzv4Q8klPviZsq1Wwqx3atXRe++FLvNq8t4NIRkcKtZ7219CBEjliUWg KCZy62/iVZkSiFMdmuC9IME4bgBFYrhkznuKRT8ZUFwRaK8pW55FAEMYhYxNMWR+FX7O xLeLZJ8J1MUWpW6iWmMQvvKpUD3KW/94AEaiRRtvTA3NaLUV9m6oZImYXYYsxhmrVZDp qTNw== MIME-Version: 1.0 Received: by 2002:adf:e44b:0:0:0:0:0 with HTTP; Mon, 6 Aug 2018 19:22:18 -0700 (PDT) From: Jim Wilson Date: Tue, 07 Aug 2018 02:22:00 -0000 Message-ID: Subject: contributing the RISC-V linux native port To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-08/txt/msg00016.txt.bz2 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. Jim