From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68536 invoked by alias); 8 Aug 2018 02:12:31 -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 67551 invoked by uid 89); 8 Aug 2018 02:12:30 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=caveat, personal X-HELO: mail-wr1-f68.google.com Received: from mail-wr1-f68.google.com (HELO mail-wr1-f68.google.com) (209.85.221.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Aug 2018 02:12:29 +0000 Received: by mail-wr1-f68.google.com with SMTP id c13-v6so583444wrt.1 for ; Tue, 07 Aug 2018 19:12:29 -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:cc; bh=jgIoMnipmbi6P9JCA2wICJHF0hX7HhpQ+cEEgUCYIoo=; b=dAkrYWD70xavv4arIMkLvu63B/NVbwiiJfjJ1/8HXjJU+sTPFdFTaejsSbfOBB/Ccr Q5cnax2cGdwo39QLVyCLO2IXSOQ+NW57EITvrAlq7fHfMq4OEkBVDN6pxI63BTf+gFl8 WDGhUrb+TN5tvGgFl9t3Xa7skegGlCZjAhdyzlmh1J0cicRB+6tfnBrVZXlOQsQVdIR/ CLQafZvgQdodSvmBR7DTqv1IAXM6+30MeuNRsz7smmXvMULyDn5j8sN9iyd5vzgLLUHB OoprU4c7bGgeEpybO4jKG6TmgG3qoCFSPl2Si8i+K2L11Lz2cw9WJ8Pb3IO7FnTuOvEq ZfDA== MIME-Version: 1.0 Received: by 2002:adf:e44b:0:0:0:0:0 with HTTP; Tue, 7 Aug 2018 19:12:26 -0700 (PDT) From: Jim Wilson Date: Wed, 08 Aug 2018 02:12:00 -0000 Message-ID: Subject: [PATCH 0/5] RISC-V Linux native port To: gdb-patches@sourceware.org Cc: Jim Wilson Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-08/txt/msg00136.txt.bz2 Here are my current patches to add the RISC-V Linux native support to gdb. These have been tested on a Hifive Unleashed running Fedora as previously mentioned and are working reasonably well. One caveat I should mention here is that this port requires multiple Linux kernel patches and a GLIBC patch, which people may not already have. I'm not sure how to handle that. I have a README.md in my personal github repo that points at the patches. There is 1 linux kernel patch that was added in the previous merge window, 2 being added in the current merge window, and one I haven't submitted yet for FP register support because it needs some cleanup work before upstreaming. There is also a glibc patch that was just added last week. Jim