From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 110267 invoked by alias); 8 Sep 2016 09:17:56 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 110250 invoked by uid 89); 8 Sep 2016 09:17:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=prototypes, vendors, HTo:U*libffi-discuss, H*Ad:U*libffi-discuss X-HELO: mail-it0-f45.google.com Received: from mail-it0-f45.google.com (HELO mail-it0-f45.google.com) (209.85.214.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 08 Sep 2016 09:17:45 +0000 Received: by mail-it0-f45.google.com with SMTP id e124so68785601ith.0 for ; Thu, 08 Sep 2016 02:17:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=cF/omWVFOvv9PLaexdQJWMixlk2PHigfleODE5KcQ+M=; b=CcEqbHH1p+kmUbibzcoTm/PnlMH68su488HQtTLi2/Nhh9aBLX63bn/xWXjSjJe50V UTMkiMMH4ks8KPbWyjTj7d0IUnEHl5tcHzMnN3693dSoBK37/iFJXCVAJVGkNplSDzCB 402eFFTH+Wd0LxIkExjuuNR9lZ6k+YdK8ZAz5+gbRQoT6d/Z5619kOB8gZexohepkEf8 u9SV3HYe2Q5zc7w1/koFVix9VYb5nM1c2U7AEe885U45NRZCG6eawSsEwvuMIkU9t8K7 iBm0x4e3557FEGo70E8vXcfD+lUf2oIx7q7URXZcxpoVPJ5WEL2rFhGXjWcJh0jFfQTV ZnLw== X-Gm-Message-State: AE9vXwPsqZKrFqq16d1R2ub6FZ/4e56oI9Kp09tfH65QXqG23nD7fEikWwctMTs93BqM9Z7oZPlsUhsOJcBGwA== X-Received: by 10.36.120.197 with SMTP id p188mr13105739itc.44.1473326263882; Thu, 08 Sep 2016 02:17:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.11.213 with HTTP; Thu, 8 Sep 2016 02:17:43 -0700 (PDT) From: "Stefan O'Rear" Date: Thu, 08 Sep 2016 09:17:00 -0000 Message-ID: Subject: RISC-V port To: libffi-discuss@sourceware.org Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016/txt/msg00036.txt.bz2 I have a [libffi patch](https://github.com/sorear/libffi-riscv/commit/e9639dc79.diff) which adds support for the RISC-V architecture. *I did not write* the code in this patch; it is a cleaned up and rebased version of a [port](https://github.com/riscv/riscv-libffi) by Michael Knyszek et al of UC Berkeley. RISC-V is a free and open standard instruction set architecture originally developed at UC Berkeley and now seeing significant interest from independent hardware vendors, with interoperable prototypes from several independent groups. Alex Bradbury's [recent RFC to the LLVM community](http://lists.llvm.org/pipermail/llvm-dev/2016-August/103748.html) has a much better explanation of what RISC-V is and why you should care about it. While the privileged architecture is still in some flux, the architecture which is visible to user space and the C calling convention have been unchanged in nearly two years and are now considered frozen, so ports like this one are very likely to remain valid. I am interested in being the responsible party to get this code into a mergable condition. I am familiar with the RISC-V ISA and calling convention and with libffi's broad principles of operation, but not with the details of libffi internals. How shall we proceed? -s