search for: wrongcode

...INK_FLAGS) main.lib assembly.lib clean: rm -f *.obj *.lib *.pdb *.dll *.map $ make -f makefile_clanglto_Oz $ llvm-pdbutil dump -l main.pdb Lines ============================================================ Mod 0000 | `assembly.obj`: Mod 0001 | `/home/jshi19/llvm/wrongcode/lld-link5/lto.tmp`: /home/jshi19/llvm/wrongcode/lld-link5/main.c (MD5: 5F82BB79FE2DA0B0549B784CFDC37D05) 0001:00000004-0000001E, line/addr entries = 5 3 00000004 ! 0 00000008 ! 5 0000000D ! 0 00000012 ! 9 00000017 ! If we disable the optimization in the CC_FLAGS with -O0 as belo...

...ain.dll /Machine:X64 /DLL /ENTRY:main /DEBUG:GHASH /lldmap main.obj assembly.obj Check to see that there are line zeros in the pdb file: $ llvm-pdbutil" dump -l main.pdb Lines ============================================================ Mod 0000 | `/home/jshi19/llvm/wrongcode/lld_PDB_issue/main.obj`: /home/jshi19/llvm/wrongcode/lld_PDB_issue/main.c (MD5: 5F82BB79FE2DA0B0549B784CFDC37D05) 0001:00000000-0000001A, line/addr entries = 5 3 00000000 ! 0 00000004 ! 5 00000009 ! 0 0000000E ! 9 00000013 ! Thanks Shi, Steven From: Zachary Turner <zturner...

...EBUG:GHASH /lldmap main.lib assembly.lib $ /home/jshi19/llvm/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/llvm-pdbutil dump -l main.pdb Lines ============================================================ Mod 0000 | `assembly.obj`: Mod 0001 | `/home/jshi19/llvm/wrongcode/lld-link5/lto.tmp`: /home/jshi19/llvm/wrongcode/lld-link5/main.c (MD5: 5F82BB79FE2DA0B0549B784CFDC37D05) 0001:00000004-0000001E, line/addr entries = 5 3 00000004 ! 0 00000008 ! 5 0000000D ! 0 00000012 ! 9 00000017 ! Thanks Steven Shi > -----Original Message-----...

On Thu, 9 Jan 2020, David Blaikie via llvm-dev wrote: > +rnk who works on COFF debugging things. > >  My understanding is that this has nothing to do with the linker - but is a > function of LLVM optimizations creating line zero debug locations. I believe > rnk & folks have disabled line zero emission for CodeView debug info in some > manner - perhaps that needs a flag? or

...o.obj /NOLOGO /NODEFAULTLIB /IGNORE:4001 /OPT:REF /OPT:ICF=10 /ALIGN:32 /SECTION:.xdata,D /SECTION:.pdata,D /DLL /ENTRY:main /SUBSYSTEM:EFI_BOOT_SERVICE_DRIVER /SAFESEH:NO /BASE:0 /DRIVER: /DEBUG:GHASH /MACHINE:X86 lld-link: error: undefined symbol: _Foo >>> referenced by /home/jshi19/llvm/wrongcode/lld-link/main.c:4 >>> main.obj:(_main) BTW, I find the lld-link does not suppor the /MAP option to generate mapfile. If I hope to output the linking mapfile info, what option should I use? Thanks Steven -------------- next part -------------- An HTML attachment was scrubb...

...ange the `memcpy` to > `foobar` in memcpy.c, the lld-link report linking 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...

Hi Steven, One thing I noticed is that you are defining `memcpy`, which clang has an intrinsic with the same name. Can you try renaming it to a random name, like `foobar`, to see if the problem still exists? On Tue, Jul 16, 2019 at 10:10 AM Shi, Steven <steven.shi at intel.com> wrote: > I’ve submitted a BZ for this issue as below: > > > > Bug 42626 - lld-link crash when

...ange the `memcpy` to > `foobar` in memcpy.c, the lld-link report linking 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...

...IGN:32 /SECTION:.xdata,D > > /SECTION:.pdata,D /DLL /ENTRY:main > /SUBSYSTEM:EFI_BOOT_SERVICE_DRIVER > > /SAFESEH:NO /BASE:0 /DRIVER: /DEBUG:GHASH /MACHINE:X86 > > > > lld-link: error: undefined symbol: _Foo > > > > >>> referenced by /home/jshi19/llvm/wrongcode/lld-link/main.c:4 > > > > >>>               main.obj:(_main) > > For 32 bit windows, functions with cdecl calling convention (the default > in C) are decorated with an underscore prefix. So you'd need to update > your nasm source file to define the symbol _Foo...

...ort linking 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 >>&g...