Displaying 2 results from an estimated 2 matches for "_clanglto38_x64_nasm_flags".
Did you mean:
_clanglto38_x64_asm_flags
2016 May 13
2
How to debug if LTO generate wrong code?
...$(BASE_NAME).map -Wl,-melf_x86_64 -Wl,--oformat=elf64-x86-64
*_CLANGLTO38_X64_ASM_FLAGS = -c -x assembler -imacros $(DEST_DIR_DEBUG)/AutoGen.h -m64 -target x86_64-pc-linux-gnu
*_CLANGLTO38_X64_RC_FLAGS = -I binary -O elf64-x86-64 -B i386 --rename-section .data=.hii
*_CLANGLTO38_X64_NASM_FLAGS = -f elf64
Steven Shi
Intel\SSG\STO\UEFI Firmware
Tel: +86 021-61166522
iNet: 821-6522
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160513/cf7649a6/attachment.html>
2016 May 16
2
How to debug if LTO generate wrong code?
...NGLTO38_X64_ASM_FLAGS = -c -x assembler -imacros
> > $(DEST_DIR_DEBUG)/AutoGen.h -m64 -target x86_64-pc-linux-gnu
> >
> > *_CLANGLTO38_X64_RC_FLAGS = -I binary -O elf64-x86-64 -B
> > i386 --rename-section .data=.hii
> >
> > *_CLANGLTO38_X64_NASM_FLAGS = -f elf64
> >
> >
> >
> >
> >
> >
> >
> > Steven Shi
> >
> > Intel\SSG\STO\UEFI Firmware
> >
> >
> >
> > Tel: +86 021-61166522
> >
> > iNet: 821-6522
> >
> >
>...