From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23656 invoked by alias); 27 May 2014 16:43:50 -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 23641 invoked by uid 89); 27 May 2014 16:43:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,RDNS_DYNAMIC autolearn=no version=3.3.2 X-HELO: ds.vvi.com Received: from 173-167-71-114-centralpennsylvania.hfc.comcastbusiness.net (HELO ds.vvi.com) (173.167.71.114) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 27 May 2014 16:43:48 +0000 Received: from localhost (localhost [127.0.0.1]) by ds.vvi.com (Postfix) with ESMTP id 861493A4317 for ; Tue, 27 May 2014 12:43:46 -0400 (EDT) Received: from ds.vvi.com ([127.0.0.1]) by localhost (ds.vvi.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ORheQgHZOyO for ; Tue, 27 May 2014 12:43:46 -0400 (EDT) Received: from [192.168.1.3] (unknown [192.168.1.3]) by ds.vvi.com (Postfix) with ESMTPSA id 0F45F3A430D for ; Tue, 27 May 2014 12:43:46 -0400 (EDT) From: Ed VanVliet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: libffi-3.1 on iOS Message-Id: <78ECC115-FDDC-493D-8E2B-00745978E522@vvi.com> Date: Tue, 27 May 2014 16:43:00 -0000 To: libffi-discuss@sourceware.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) X-SW-Source: 2014/txt/msg00057.txt.bz2 Dear libffi crew, Bug report: I just tried libffi-3.1 and it produced the issues below. Can the warnings be eliminated and the link error fixed? Sincerely, Ed --------------------------- Running libffi on iOS (iPhone) simulator works for both 32 and 64 bit simul= ators using libffi-3.0.14-rc0 But, with libffi-3.1 it works for 64 bit simulator, but fails to link for 3= 2 bit simulator; giving the following: (null): "_ffi_call_win32", referenced from: (null): "_ffi_closure_FASTCALL", referenced from: (null): "_ffi_closure_STDCALL", referenced from: (null): "_ffi_closure_THISCALL", referenced from: (null): Linker command failed with exit code 1 (use -v to see invocation) Also, on both the 32 and 64 bit segments the linker gives this warning: (null): Could not create compact unwind for .LFB3: non-standard register 5 = being saved in prolog which it gave for both 3.0.14-rc0 and 3.1. However, the warning does not se= em to cause a problem. On the ARM target the linker gives the following warnings: ld: warning: arm64 function not 4-byte aligned: ltmp0 from /libffi.a(sysv_a= rm64.o) ld: warning: arm64 function not 4-byte aligned: _ffi_call_SYSV from /libffi= .a(sysv_arm64.o) ld: warning: arm64 function not 4-byte aligned: _ffi_closure_SYSV from /lib= ffi.a(sysv_arm64.o) which also do not seem to cause a problem. It would be nice to fix the build and code so it didn't produce the error a= nd warnings.