From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 77438 invoked by alias); 1 Nov 2016 20:52:50 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 77420 invoked by uid 89); 1 Nov 2016 20:52:49 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=dates, painless, our, morning X-HELO: mail-pf0-f177.google.com Received: from mail-pf0-f177.google.com (HELO mail-pf0-f177.google.com) (209.85.192.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 01 Nov 2016 20:52:39 +0000 Received: by mail-pf0-f177.google.com with SMTP id d2so25933307pfd.0 for ; Tue, 01 Nov 2016 13:52:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:cc:to:cc:subject :in-reply-to; bh=u9WcXZSMTOv0j6d4heh1rYKDx/zLj1rfcmlI8eEn5Qk=; b=bJXF9Fg39BDmlSSrwzHtFbV+lXW3jbDqLyF1siMH9GUnnQqt0vlFYHibyfdgA2xKQx lo4plBjcskT6ftrrKXT1OPLNloa5iOlKm1ITm6+8clkVnnhTywKlCd6Gq2aPiAJjP/7N cQ2bD1HY+kjks+YWunCQ+OMJ40aPMmY6jMf41wHFhEUnsFYLUfjKr4MrSVd4bT92EXjo BG7+eTuCQboKyisV/MadvIWLpHmbdaGLCS+H90ul21kzv0G2YheBlIADXC0HnEGY7qtE dP+4PynRtidspxFOMUhoivWkdNclJc3OL/80DjM8ibjLD20oVTIKcnfjaR/lRu9rwpcn oe6Q== X-Gm-Message-State: ABUngvdWZ83dmgC1Oe7sBpp4+tLZ2L2i7izoksgz/C5c6gDlQrCsdjb4hTf1bt8xhGPQgQ== X-Received: by 10.99.47.7 with SMTP id v7mr52547472pgv.15.1478033557957; Tue, 01 Nov 2016 13:52:37 -0700 (PDT) Received: from localhost (wap-cal.CS.Berkeley.EDU. [128.32.35.228]) by smtp.gmail.com with ESMTPSA id 73sm44167503pfn.45.2016.11.01.13.52.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Nov 2016 13:52:37 -0700 (PDT) Message-ID: <58190095.cc0d620a.59ab5.bf99@mx.google.com> X-Google-Original-Message-ID: Mime-Version: 1.0 (MHng) Date: Tue, 01 Nov 2016 20:52:00 -0000 X-Google-Original-Date: Tue, 01 Nov 2016 13:52:35 PDT (-0700) From: Palmer Dabbelt CC: Andrew Waterman To: gdb-patches@sourceware.org CC: amodra@gmail.com Subject: Re: GDB port for RISC-V In-Reply-To: <1477179592-32501-1-git-send-email-palmer@dabbelt.com> X-SW-Source: 2016-11/txt/msg00004.txt.bz2 On Sat, 22 Oct 2016 16:39:50 PDT (-0700), Palmer Dabbelt wrote: > This message is "In-Reply-To" a larger patch set that contains a whole binutils > port for RISC-V. During our original patch submission it was suggested we send > the patches relevant to GDB to this mailing list, which is why you might not > have seen the v1 patches. > > While there are a few things left to do on our end, I'd like to submit a v2 of > the patch set (the first submission to the GDB mailing list) just so we're all > on the same page. The exact commit I'm sending is availiable here: > > https://github.com/riscv/riscv-binutils-gdb/commit/a949ca81ca7eca890e27d85d729203253d7862dd > > while the whole binutils port, including both the patches submitted to the > binutils mailing list and the autogenerated files necessary for me to build the > RISC-V port, is availiable here: > > https://github.com/riscv/riscv-binutils-gdb/tree/riscv-for-upstream-v2 > > Aside from review on this mailing list, there are a few problems pointed out by > our first submission that haven't been addresses yet: > > * riscv-opc.h is autogenerated from a Python script. We will either clean up > this script enough to be suitable for submission, or will write some CPP > that produces a similar result. > > * I forgot to fix copyright dates, but I've already made it this far into the > email... The plan is to only extend copyrights, and mark every committed > file as changed in 2016 if it's not already. > > Additionally, there are a few issues on our github that are relevant, but I'm > not sure if they block upstreaming: > > * https://github.com/riscv/riscv-gnu-toolchain/issues/124 : "sizeof(long > double)" is 64-bit on RISC-V, which precludes the use of the Q extension for > 128-bit floating point. This may cause an ABI-breakage. > > * https://github.com/riscv/riscv-gnu-toolchain/pull/136 : The path for ld.so > might change. This would definately be an ABI change. > > Thanks to everyone who has provided feedback from the other list, hopefully > this one will be as painless :). > > [PATCH 1/2] RISC-V GDB Port > [PATCH 2/2] RISC-V GDB Simulator Port Upstream has merged the RISC-V binutils port as of this morning. I haven't gotten any feedback on our GDB submission as of yet. Is there anything I can do to help our GDB port make it upstream as well?