Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Liming Gao
Fish: From: af...@apple.com [mailto:af...@apple.com] Sent: Thursday, June 6, 2019 11:39 AM To: devel@edk2.groups.io; Lu, XiaoyuX Cc: Gao, Liming ; Bi, Dandan ; Wang, Jian J Subject: Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem On Jun 4, 2019, at

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Andrew Fish via Groups.Io
x...@intel.com>> >> Cc: Bi, Dandan mailto:dandan...@intel.com>>; Wang, >> Jian J mailto:jian.j.w...@intel.com>> >> Subject: RE: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix >> CLANG38 IA32 build problem >> >> Xiaoyu: >&g

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Liming Gao
PM > > To: Gao, Liming ; devel@edk2.groups.io > > Cc: Bi, Dandan ; Wang, Jian J > > Subject: RE: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix > > CLANG38 IA32 build problem > > > > Yes I verify them. > > > > build -p OvmfPkg/OvmfPkgX64.dsc -

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Liming Gao
Liming > > Sent: Wednesday, June 5, 2019 3:37 PM > > To: Lu, XiaoyuX ; devel@edk2.groups.io > > Cc: Bi, Dandan ; Wang, Jian J > > Subject: RE: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix > > CLANG38 IA32 build problem > > > > Do you cover IA

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Xiaoyu Lu
Cc: Bi, Dandan ; Wang, Jian J > Subject: RE: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix > CLANG38 IA32 build problem > > Do you cover IA32 & X64 arch both, and verify Ovmf boot? > > > -Original Message- > > From: Lu, XiaoyuX > > Sent:

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Liming Gao
oPkg/IntrinsicLib: Fix CLANG38 > IA32 build problem > > Liming, > > > -Original Message- > > From: Gao, Liming > > Sent: Wednesday, June 5, 2019 3:28 PM > > To: Lu, XiaoyuX ; devel@edk2.groups.io > > Cc: Bi, Dandan ; Wang, Jian J > > Subject: R

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Xiaoyu Lu
Liming, > -Original Message- > From: Gao, Liming > Sent: Wednesday, June 5, 2019 3:28 PM > To: Lu, XiaoyuX ; devel@edk2.groups.io > Cc: Bi, Dandan ; Wang, Jian J > Subject: RE: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix > CLANG38 IA32 buil

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-05 Thread Liming Gao
Xiaoyu: > -Original Message- > From: Lu, XiaoyuX > Sent: Wednesday, June 5, 2019 2:34 PM > To: Gao, Liming ; devel@edk2.groups.io > Cc: Bi, Dandan ; Wang, Jian J > Subject: RE: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 > IA32 build p

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-04 Thread Xiaoyu Lu
Hi Liming, > -Original Message- > From: Gao, Liming > Sent: Wednesday, June 5, 2019 1:57 PM > To: devel@edk2.groups.io; Lu, XiaoyuX > Cc: Bi, Dandan ; Wang, Jian J > Subject: RE: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix > CLANG38 IA32 buil

Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-04 Thread Liming Gao
Xiaoyu: >-Original Message- >From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of >Xiaoyu Lu >Sent: Wednesday, June 05, 2019 1:25 PM >To: devel@edk2.groups.io >Cc: Lu, XiaoyuX ; Bi, Dandan ; >Wang, Jian J >Subject: [edk2-devel] [PATCH v1 1/1] Cry

[edk2-devel] [PATCH v1 1/1] CryptoPkg/IntrinsicLib: Fix CLANG38 IA32 build problem

2019-06-04 Thread Xiaoyu Lu
When use clang-3.8 to build the NetworkPkg, compiler optimization may use memcpy for memory copy. For example: CryptoPkg/Library/OpensslLib/openssl/ssl/ssl_rsa.c:918: undefined reference to `memcpy'` Compiler optimization is sophisticated, but we can work around it use __attribute__((__used__))