search for: releaseinstall

...ss = 0; Snp->MapList[Index].MapCookie = 0; } return 0; } $ cat intrinsics.c void * memset (void *dest, int ch, size_t count) { volatile char *Pointer; Pointer = (char *)dest; while (count-- != 0) { *(Pointer++) = (char)ch; } return dest; } $ "/home/jshi19/llvm/releaseinstall/bin/clang-cl" /Fomain.obj /c --target=x86_64-pc-win32-coff -m64 /O1b2s -flto main.c $ "/home/jshi19/llvm/releaseinstall/bin/clang-cl" /Fointrinsics.obj /c --target=x86_64-pc-win32-coff -m64 /O1b2s -flto intrinsics.c $ "/home/jshi19/llvm/releaseinstall/bin/llvm-lib" /OUT:int...

...*Pointer; >> >> Pointer = (char *)dest; >> >> while (count-- != 0) { >> >> *(Pointer++) = (char)ch; >> >> } >> >> return dest; >> >> } >> >> >> >> >> >> $ "/home/jshi19/llvm/releaseinstall/bin/clang-cl" /Fomain.obj /c >> --target=x86_64-pc-win32-coff -m64 /O1b2s -flto main.c >> >> $ "/home/jshi19/llvm/releaseinstall/bin/clang-cl" /Fointrinsics.obj /c >> --target=x86_64-pc-win32-coff -m64 /O1b2s -flto intrinsics.c >> >> $ "/home/...

...ng error that it cannot find > the _memcpy symbol as below. In uefi firmware, we have to explicitly > implement these compiler intrinsic functions by ourselves. > > > > > > jshi19 at ub2-uefi-b01:~/llvm/wrongcode/lld-link3$ make > > "/home/jshi19/llvm/llvm-project/releaseinstall/bin/clang" -Oz -flto > -target i686-unknown-windows -c -o main.obj main.c > > "/home/jshi19/llvm/llvm-project/releaseinstall/bin/clang" -Oz -flto > -target i686-unknown-windows -c -o memcpy.obj memcpy.c > > "/home/jshi19/llvm/llvm-project/releaseinstall/bin/l...

...going on. On Tue, Jul 16, 2019 at 9:00 PM Shi, Steven <steven.shi at intel.com> wrote: > In my previous test case, after add the `-fno-builtin` to clang then > build, the lld-link still has same crash as below: > > > > $ make > > "/home/jshi19/llvm/llvm-project/releaseinstall/bin/clang" -Oz -flto > -target i686-unknown-windows -fno-builtin -c -o main.obj main.c > > "/home/jshi19/llvm/llvm-project/releaseinstall/bin/clang" -Oz -flto > -target i686-unknown-windows -fno-builtin -c -o memcpy.obj memcpy.c > > "/home/jshi19/llvm/llvm-pr...

...at memcpy.c > > typedef unsigned int size_t; > > void *memcpy(void *dest, const void *src, size_t n) > > { > > return 0; > > } > > > > $ cat makefile > > CC_FLAGS= -Oz -flto -target i686-unknown-windows > > CC = /home/jshi19/llvm/llvm-project/releaseinstall/bin/clang > > DLINK_FLAGS = /MACHINE:X86 /DLL /ENTRY:TlsDriverEntryPoint > > DLINK = /home/jshi19/llvm/llvm-project/releaseinstall/bin/lld-link > > SLINK_FLAGS = > > SLINK = /home/jshi19/llvm/llvm-project/releaseinstall/bin/llvm-lib > > > > build: > >...

...urce = (void*)cryptopro_ext; while (length--) { *(ret++) = *(Source++); } } $ cat memcpy.c typedef unsigned int size_t; void *memcpy(void *dest, const void *src, size_t n) { return 0; } $ cat makefile CC_FLAGS= -Oz -flto -target i686-unknown-windows CC = /home/jshi19/llvm/llvm-project/releaseinstall/bin/clang DLINK_FLAGS = /MACHINE:X86 /DLL /ENTRY:TlsDriverEntryPoint DLINK = /home/jshi19/llvm/llvm-project/releaseinstall/bin/lld-link SLINK_FLAGS = SLINK = /home/jshi19/llvm/llvm-project/releaseinstall/bin/llvm-lib build: "$(CC)" $(CC_FLAGS) -c -o main.obj main.c &quot...

...t intel.com> wrote: >> >>> In my previous test case, after add the `-fno-builtin` to clang then >>> build, the lld-link still has same crash as below: >>> >>> >>> >>> $ make >>> >>> "/home/jshi19/llvm/llvm-project/releaseinstall/bin/clang" -Oz -flto >>> -target i686-unknown-windows -fno-builtin -c -o main.obj main.c >>> >>> "/home/jshi19/llvm/llvm-project/releaseinstall/bin/clang" -Oz -flto >>> -target i686-unknown-windows -fno-builtin -c -o memcpy.obj memcpy.c >>&...

...my problem in linux. The example has two only source files: main.c and foo.nasm. $ cat main.c void Foo (void); int main() { Foo(); return 0; } $ cat foo.nasm SECTION .text global Foo Foo: Ret 64bits compiling and linking is successful: $ nasm foo.nasm -Ox -f win64 -g -o foo.obj $ ~/llvm/releaseinstall/bin/clang-cl main.c /nologo /c /WX /GS- /W4 /Gs32768 /D UNICODE /O1b2s /EHs-c- /GR- /GF /Gy /Zi /Gw -m64 $ ~/llvm/releaseinstall/bin/lld-link main.obj foo.obj /NOLOGO /NODEFAULTLIB /IGNORE:4001 /OPT:REF /OPT:ICF=10 /ALIGN:32 /SECTION:.xdata,D /SECTION:.pdata,D /DLL /ENTRY:main /SUBSYSTEM:EFI_BOOT_S...

...ent as 4096 in COFF file and let the lld-link respect the user's /ALIGN option value? We can set the 4096 as the default SectionAlignment value. Below are some steps to show the hardcode issue and code size impact: $ cat main.c int main() { return 0; } $ "/home/jshi19/llvm/llvm-project/releaseinstall/bin/clang" -target i686-unknown-windows -fno-builtin -c -o main.obj main.c $ "/home/jshi19/llvm/llvm-project/releaseinstall/bin/lld-link" /OUT:main.dll /MACHINE:X86 /DLL /ENTRY:main /ALIGN:32 /FILEALIGN:32 main.obj $ sudo apt install pev $ readpe -H main.dll ... Alignment of sec...

...entries, are all 0. In other word, I found the S in below R_X86_64_64 calculation is 0. Name: R_X86_64_64 1 word64 S + A Below is an example to compare the lld and ld, sorry about the verbose. 1. Firstly, I use lld to link a HelloWorld module with -pie enabled: "/home/jshi19/llvm/releaseinstall/bin/ld.lld" -pie -z relro --hash-style=gnu --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o /home/jshi19/wksp_efi/lgao4/edk2/Build/OvmfX64/NOOPT_CLANG38/X64/MdeModulePkg/Application/HelloWorld/HelloWorld/DEBUG/HelloWorld.dll -u _ModuleEntryPoint -L/usr/lib/gcc/x86_64...

....nasm > > > >     SECTION .text > > > > global Foo > > > > Foo: > > > > Ret > > > > > > > > 64bits compiling and linking is successful: > > > > $ nasm foo.nasm -Ox -f win64 -g -o foo.obj > > > > $ ~/llvm/releaseinstall/bin/clang-cl main.c /nologo /c /WX /GS- /W4 > /Gs32768 > > /D UNICODE /O1b2s /EHs-c- /GR- /GF /Gy /Zi /Gw -m64 > > > > $ ~/llvm/releaseinstall/bin/lld-link main.obj foo.obj /NOLOGO > /NODEFAULTLIB > > /IGNORE:4001 /OPT:REF /OPT:ICF=10 /ALIGN:32 /SECTION:.xdata,D > &...

...entries, are all 0. In other word, I found the S in below R_X86_64_64 calculation is 0. Name: R_X86_64_64 1 word64 S + A Below is an example to compare the lld and ld, sorry about the verbose. 1. Firstly, I use lld to link a HelloWorld module with -pie enabled: "/home/jshi19/llvm/releaseinstall/bin/ld.lld" -pie -z relro --hash-style=gnu --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o /home/jshi19/wksp_efi/lgao4/edk2/Build/OvmfX64/NOOPT_CLANG38/X64/MdeModulePkg/Application/HelloWorld/HelloWorld/DEBUG/HelloWorld.dll -u _ModuleEntryPoint -L/usr/lib/gcc/x86_64...

...entries, are all 0. In other word, I found the S in below R_X86_64_64 calculation is 0. Name: R_X86_64_64 1 word64 S + A Below is an example to compare the lld and ld, sorry about the verbose. 1. Firstly, I use lld to link a HelloWorld module with -pie enabled: "/home/jshi19/llvm/releaseinstall/bin/ld.lld" -pie -z relro --hash-style=gnu --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o /home/jshi19/wksp_efi/lgao4/edk2/Build/OvmfX64/NOOPT_CLANG38/X64/MdeModulePkg/Application/HelloWorld/HelloWorld/DEBUG/HelloWorld.dll -u _ModuleEntryPoint -L/usr/lib/gcc/x86_64...