maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/COFF/pdb-same-name.test

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

24 lines
1004 B
Plaintext
Raw Normal View History

COFF: PDB: Allow multiple modules with the same name. It is possible for two modules to have the same name if they are archive members with the same name, or if we are doing LTO (in which case all modules will have the name "lto.tmp"). Differential Revision: https://reviews.llvm.org/D37589 llvm-svn: 312744
2017-09-08 04:39:46 +08:00
# RUN: rm -rf %t1 %t2
# RUN: mkdir %t1 %t2
[test] Replace `yaml2obj >` with `yaml2obj -o` and remove unneeded input redirection
2020-08-21 06:00:25 +08:00
# RUN: yaml2obj %p/Inputs/pdb1.yaml -o %t1/foo.obj
COFF: PDB: Allow multiple modules with the same name. It is possible for two modules to have the same name if they are archive members with the same name, or if we are doing LTO (in which case all modules will have the name "lto.tmp"). Differential Revision: https://reviews.llvm.org/D37589 llvm-svn: 312744
2017-09-08 04:39:46 +08:00
# RUN: llvm-ar cru %t1/foo.lib %t1/foo.obj
[test] Replace `yaml2obj >` with `yaml2obj -o` and remove unneeded input redirection
2020-08-21 06:00:25 +08:00
# RUN: yaml2obj %p/Inputs/pdb2.yaml -o %t2/foo.obj
COFF: PDB: Allow multiple modules with the same name. It is possible for two modules to have the same name if they are archive members with the same name, or if we are doing LTO (in which case all modules will have the name "lto.tmp"). Differential Revision: https://reviews.llvm.org/D37589 llvm-svn: 312744
2017-09-08 04:39:46 +08:00
# RUN: llvm-ar cru %t2/foo.lib %t2/foo.obj
# RUN: rm -f %t.dll %t.pdb
# RUN: lld-link /debug /pdb:%t.pdb /dll /out:%t.dll /entry:main /nodefaultlib \
# RUN: %t1/foo.lib %t2/foo.lib
# RUN: llvm-pdbutil dump -modules %t.pdb | FileCheck -check-prefix RAW %s
RAW: Modules
RAW-NEXT: ============================================================
RAW-NEXT: Mod 0000 | `foo.obj`:
Better support for POSIX paths in PDBs. This a resubmission of a patch which was previously reverted due to breaking several lld tests. The issues causing those failures have been fixed, so the patch is now resubmitted. ---Original Commit Message--- While it doesn't make a *ton* of sense for POSIX paths to be in PDBs, it's possible to occur in real scenarios involving cross compilation. The tools need to be able to handle this, because certain types of debugging scenarios are possible without a running process and so don't necessarily require you to be on a Windows system. These include post-mortem debugging and binary forensics (e.g. using a debugger to disassemble functions and examine symbols without running the process). There's changes in clang, LLD, and lldb in this patch. After this the cross-platform disassembly and source-list tests pass on Linux. Furthermore, the behavior of LLD can now be summarized by a much simpler rule than before: Unless you specify /pdbsourcepath and /pdbaltpath, the PDB ends up with paths that are valid within the context of the machine that the link is performed on. Differential Revision: https://reviews.llvm.org/D53149 llvm-svn: 344377
2018-10-13 01:26:19 +08:00
RAW-NEXT: Obj: `{{.*}}1{{[\\/]}}foo.lib`:
[PDB] Make our PDBs look more like MS PDBs. When investigating bugs in PDB generation, the first step is often to do the same link with link.exe and then compare PDBs. But comparing PDBs is hard because two completely different byte sequences can both be correct, so it hampers the investigation when you also have to spend time figuring out not just which bytes are different, but also if the difference is meaningful. This patch fixes a couple of cases related to string table emission, hash table emission, and the order in which we emit strings that makes more of our bytes the same as the bytes generated by MS PDBs. Differential Revision: https://reviews.llvm.org/D44810 llvm-svn: 328348
2018-03-24 02:43:39 +08:00
RAW-NEXT: debug stream: 11, # files: 1, has ec info: false
COFF: PDB: Allow multiple modules with the same name. It is possible for two modules to have the same name if they are archive members with the same name, or if we are doing LTO (in which case all modules will have the name "lto.tmp"). Differential Revision: https://reviews.llvm.org/D37589 llvm-svn: 312744
2017-09-08 04:39:46 +08:00
RAW-NEXT: pdb file ni: 0 ``, src file ni: 0 ``
RAW-NEXT: Mod 0001 | `foo.obj`:
Better support for POSIX paths in PDBs. This a resubmission of a patch which was previously reverted due to breaking several lld tests. The issues causing those failures have been fixed, so the patch is now resubmitted. ---Original Commit Message--- While it doesn't make a *ton* of sense for POSIX paths to be in PDBs, it's possible to occur in real scenarios involving cross compilation. The tools need to be able to handle this, because certain types of debugging scenarios are possible without a running process and so don't necessarily require you to be on a Windows system. These include post-mortem debugging and binary forensics (e.g. using a debugger to disassemble functions and examine symbols without running the process). There's changes in clang, LLD, and lldb in this patch. After this the cross-platform disassembly and source-list tests pass on Linux. Furthermore, the behavior of LLD can now be summarized by a much simpler rule than before: Unless you specify /pdbsourcepath and /pdbaltpath, the PDB ends up with paths that are valid within the context of the machine that the link is performed on. Differential Revision: https://reviews.llvm.org/D53149 llvm-svn: 344377
2018-10-13 01:26:19 +08:00
RAW-NEXT: Obj: `{{.*}}2{{[\\/]}}foo.lib`:
[PDB] Make our PDBs look more like MS PDBs. When investigating bugs in PDB generation, the first step is often to do the same link with link.exe and then compare PDBs. But comparing PDBs is hard because two completely different byte sequences can both be correct, so it hampers the investigation when you also have to spend time figuring out not just which bytes are different, but also if the difference is meaningful. This patch fixes a couple of cases related to string table emission, hash table emission, and the order in which we emit strings that makes more of our bytes the same as the bytes generated by MS PDBs. Differential Revision: https://reviews.llvm.org/D44810 llvm-svn: 328348
2018-03-24 02:43:39 +08:00
RAW-NEXT: debug stream: 12, # files: 1, has ec info: false
COFF: PDB: Allow multiple modules with the same name. It is possible for two modules to have the same name if they are archive members with the same name, or if we are doing LTO (in which case all modules will have the name "lto.tmp"). Differential Revision: https://reviews.llvm.org/D37589 llvm-svn: 312744
2017-09-08 04:39:46 +08:00
RAW-NEXT: pdb file ni: 0 ``, src file ni: 0 ``