From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76313 invoked by alias); 18 Apr 2015 06:29:48 -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 76303 invoked by uid 89); 18 Apr 2015 06:29:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.7 required=5.0 tests=AWL,BAYES_05,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f182.google.com Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Sat, 18 Apr 2015 06:29:46 +0000 Received: by wizk4 with SMTP id k4so43929876wiz.1 for ; Fri, 17 Apr 2015 23:29:43 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.161.138 with SMTP id xs10mr12404314wjb.37.1429338583756; Fri, 17 Apr 2015 23:29:43 -0700 (PDT) Received: by 10.194.29.65 with HTTP; Fri, 17 Apr 2015 23:29:43 -0700 (PDT) Date: Sat, 18 Apr 2015 06:29:00 -0000 Message-ID: Subject: Questions about the libffi development process From: Russell Keith-Magee To: libffi-discuss@sourceware.org Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015/txt/msg00053.txt.bz2 I've got 2 questions about the libffi development process. 1. A recent commit: https://github.com/atgreen/libffi/commit/a4b785ea (authored by Richard Henderson) appears to have broken ARMv7 support to the point where libffi doesn't build. (Or, at least, it raises a syntax error on iOS - but I can't see any reason the same problem wouldn't exist for other ARM platforms). The problem has been logged as #181: https://github.com/atgreen/libffi/issues/181 Unfortunately, I don't have the expertise to fix this problem myself, and it's not clear from the discussion that the problem has been acknowledged by anyone in a position to fix it, or that it will be considered a release blocking bug for a future release. Is there anything I can/should do to bring attention to this problem and/or mark it as a showstopper (other than what has already been done on the ticket and in this email)? 2. I can see the version number in the README was bumped to 4 just after the 3.2.1 release - but what is the state of planning around a formal v4 release (or whatever the next version will be)? Is there a vague target date? A TODO list to be cleared off? Or just general "whenever it's ready" guidance? Yours, Russ Magee %-)