From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11962 invoked by alias); 18 Jun 2019 14:05:27 -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 11954 invoked by uid 89); 18 Jun 2019 14:05:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,SPAM_BODY1,SPF_PASS autolearn=no version=3.3.1 spammy=H*Ad:U*libffi-discuss, senior, Senior, Solutions X-HELO: mga09.intel.com Received: from mga09.intel.com (HELO mga09.intel.com) (134.134.136.24) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 18 Jun 2019 14:05:25 +0000 Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jun 2019 07:05:23 -0700 Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga001.fm.intel.com with ESMTP; 18 Jun 2019 07:05:22 -0700 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 18 Jun 2019 07:05:22 -0700 Received: from bgsmsx103.gar.corp.intel.com (10.223.4.130) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 18 Jun 2019 07:05:22 -0700 Received: from bgsmsx101.gar.corp.intel.com ([169.254.1.10]) by BGSMSX103.gar.corp.intel.com ([169.254.4.247]) with mapi id 14.03.0439.000; Tue, 18 Jun 2019 19:35:20 +0530 From: "Kiran, Pichika Uday" To: Anthony Green CC: "libffi-discuss@sourceware.org" , "Nallani, Prasad" , "Kunche, Kishore" Subject: RE: Contribution towards LibFFI development Date: Tue, 18 Jun 2019 14:05:00 -0000 Message-ID: <6282B4CB3C7A4A45BCD404004B58DECB58EC06@BGSMSX101.gar.corp.intel.com> References: <6282B4CB3C7A4A45BCD404004B58DECB58E40A@BGSMSX101.gar.corp.intel.com> <87tvco30m8.fsf@laptop.atgreen.org> In-Reply-To: <87tvco30m8.fsf@laptop.atgreen.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Return-Path: pichika.uday.kiran@intel.com X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00009.txt.bz2 Hi Anthony, Thanks for your reply.=20 I had gone through the notes as per your suggestion.=20=20 README.md contains the information about the platforms, compilers supported= by libffi. Here my question is about setting up the different platform in the existing= machine. Ex: If there are any issues reported on PowerPC64 but my current machine is= installed with Linux. In this case, how can I compile libffi to PowerPC64 = platform on my linux machine ? Do I need to use any simulators ? Can you pl= ease help me on this query ? I ran "make check" on ClearLinux platform and got the below failures. I'm c= hecking these issues from my side. XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D54 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O0 -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D__MSABI__ execution te= st XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D54 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O2 -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D__MSABI__ execution te= st XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D54 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O2 -fomit-frame-pointer -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D_= _MSABI__ execution test XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D55 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O0 -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D__MSABI__ execution te= st XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D55 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O2 -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D__MSABI__ execution te= st XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D55 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O2 -fomit-frame-pointer -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D_= _MSABI__ execution test XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D56 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O0 -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D__MSABI__ execution te= st XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D56 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O2 -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D__MSABI__ execution te= st XFAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=3D56 -Wn= o-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-u= ninitialized -O2 -fomit-frame-pointer -DABI_NUM=3DFFI_GNUW64 -DABI_ATTR=3D_= _MSABI__ execution test Thanks=20 Uday Kiran -----Original Message----- From: Anthony Green [mailto:green@redhat.com]=20 Sent: Monday, June 17, 2019 5:06 PM To: Kiran, Pichika Uday Cc: libffi-discuss@sourceware.org; Nallani, Prasad ; Kunche, Kishore Subject: Re: Contribution towards LibFFI development "Kiran, Pichika Uday" writes: > Myself Uday Kiran from Intel decided to contribute to libffi=20 > development and bug fixing. Hi Uday, thanks for offering to help. > Can someone please help me in providing the below details on libffi which= will help me to understand the library better. > > 1. How to setup the multiple platforms to check the bugs raised > in github libffi is configured and built using the GNU autotools. See README.md, and= have a look at the scripts in the .travis directory to get an idea of how = to use them. > 2. Is CI(Continuous integration) process happenings for libffi ? > If yes, what is the frequency of this and who is the maintainer ? We use travis and appveyor for CI, which happens on every commit. The conf= igury for those CI platforms is in the libffi github-hosted repo. They can always be improved, and if anyone has ideas as to get how more pla= tform coverage, that would be welcome. CI is a challenge for libffi. > > 3. How to verify if any fix has been made by running bunch of > test cases in-order not to disturb the existing functionality. We run the testsuite as part of the CI process. Look at .travis.yml and .a= ppveyor.yml. > Along with the above details, can someone please send me the=20 > documentation on libffi and its code flow ? There is nothing outside of documentation in the libffi git repo. Thanks, AG -- Anthony Green Senior Principal Solutions Architect, Financial Services +1 647 477-3809