search for: lldmap

...assembly_fun(); } assembly_fun(); } Then link the assembly and c functions together as below: $ clang -g -m64 -target x86_64-unknown-windows -gcodeview -O1 -c -o main.obj main.c $ nasm -f win64 -o assembly.obj assembly.nasm $ lld-link /OUT:main.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/wrong...

...N .text global assembly_fun assembly_fun: ret $ cat makefile_clanglto_Oz CC_FLAGS= -g -m64 -mcmodel=small -target x86_64-unknown-windows -gcodeview -flto -Oz CC = /home/jshi19/llvm/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/clang DLINK_FLAGS = /Machine:X64 /DLL /ENTRY:main /DEBUG:GHASH /lldmap DLINK = /home/jshi19/llvm/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/lld-link SLINK = /home/jshi19/llvm/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/llvm-lib build: "$(CC)" $(CC_FLAGS) -c -o main.obj main.c "nasm" -f win64 -o assembly.obj assembly....

...quot; /OUT:main.lib main.obj "/home/jshi19/llvm/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/llvm-lib" /OUT:assembly.lib assembly.obj "/home/jshi19/llvm/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/lld-link" /OUT:main.dll /Machine:X64 /DLL /ENTRY:main /DEBUG: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-link...

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

Hi Rui, Peter, You know I'm enabling the "clang-cl + lld-link" toolchain for Uefi firmware. I meet a problem that the lld-link fails to link 32bits assembly functions, but can link 64bits assembly functions successfully. I need your suggestion. Below is an example to show my problem in linux. The example has two only source files: main.c and foo.nasm. $ cat main.c void Foo (void);

...embly files use some sort of macro for wrapping this detail.) > > > > 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? > > lld-link has got a private option /lldmap:<filename> which does output > some sort of filename. I'm not sure what the reasons are for providing it > under a private name instead of supporting the link.exe option /map. Maybe > the format of the generated mapfile differs so that it might not work for > automatic tools t...

...OFF/include.test lld :: COFF/include2.test lld :: COFF/internal.test lld :: COFF/invalid-debug-type.test lld :: COFF/invalid-obj.test lld :: COFF/largeaddressaware.test lld :: COFF/libpath.test lld :: COFF/linkrepro-res.test lld :: COFF/linkrepro.test lld :: COFF/lldmap.test lld :: COFF/loadcfg.ll lld :: COFF/loadcfg.test lld :: COFF/loadcfg32.test lld :: COFF/locally-imported-arm64.test lld :: COFF/locally-imported-warn-multiple.s lld :: COFF/locally-imported.test lld :: COFF/locally-imported32.test lld :: COFF/long-section-name.te...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>