maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/ELF/undef.s

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

102 lines
4.4 KiB
ArmAsm
Raw Normal View History

Print member name in undefined symbol error. llvm-svn: 268976
2016-05-10 05:40:06 +08:00
# REQUIRES: x86
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t.o
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %p/Inputs/undef.s -o %t2.o
[ELF] Better error reporting for undefined symbols This patch make lld show following details for undefined symbol errors: - file (line) - file (function name) - file (section name + offset) Differential revision: https://reviews.llvm.org/D25826 llvm-svn: 285186
2016-10-26 19:07:09 +08:00
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %p/Inputs/undef-debug.s -o %t3.o
[ELF] Prevent crash when reporting errors if debug line cannot be parsed LLD uses the debug info and debug line sections to determine the location of e.g. references to undefined symbols, when producing error messages. In the event that debug info was present, but debug line parsing failed for some reason, then a nullptr would end up being dereferenced by the location-lookup code. Differential Revision: https://reviews.llvm.org/D44205 Reviewers: grimar llvm-svn: 326899
2018-03-07 23:22:58 +08:00
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %p/Inputs/undef-bad-debug.s -o %t4.o
[lld] Make tests calling llvm-ar more robust Some lit tests that call llvm-ar use the 'r' flag. If the target archive already exists and is in a corrupt state, this can cause the test to fail. We have added 'rm -f' calls before the llvm-ar calls to increase the robustness of the tests. Differential revision: https://reviews.llvm.org/D49184 llvm-svn: 338705
2018-08-02 19:33:54 +08:00
# RUN: rm -f %t2.a
Print member name in undefined symbol error. llvm-svn: 268976
2016-05-10 05:40:06 +08:00
# RUN: llvm-ar rc %t2.a %t2.o
[ELF][test] Change -o %t to -o /dev/null if the output is not needed
2020-02-13 13:48:45 +08:00
# RUN: not ld.lld %t.o %t2.a %t3.o %t4.o -o /dev/null 2>&1 \
[test][ELF] Verify debug line corruption messages are printed once LLD warns if it encounters malformed debug data when parsing line information for an undefined reference. We only want to warn once. This patch adds additional checking to make sure the warnings are printed only once, both for variables within the same program and variables in later line programs. Reviewed by: grimar, MaskRay Differential Revision: https://reviews.llvm.org/D71759
2019-12-20 21:51:18 +08:00
# RUN: | FileCheck %s --implicit-check-not="error:" --implicit-check-not="warning:"
[ELF][test] Change -o %t to -o /dev/null if the output is not needed
2020-02-13 13:48:45 +08:00
# RUN: not ld.lld -pie %t.o %t2.a %t3.o %t4.o -o /dev/null 2>&1 \
[test][ELF] Verify debug line corruption messages are printed once LLD warns if it encounters malformed debug data when parsing line information for an undefined reference. We only want to warn once. This patch adds additional checking to make sure the warnings are printed only once, both for variables within the same program and variables in later line programs. Reviewed by: grimar, MaskRay Differential Revision: https://reviews.llvm.org/D71759
2019-12-20 21:51:18 +08:00
# RUN: | FileCheck %s --implicit-check-not="error:" --implicit-check-not="warning:"
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: foo
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: {{.*}}:(.text+0x1)
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: bar
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: >>> {{.*}}:(.text+0x6)
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: foo(int)
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: >>> {{.*}}:(.text+0x10)
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
[DebugInfo] Make most debug line prologue errors non-fatal to parsing Many of the debug line prologue errors are not inherently fatal. In most cases, we can make reasonable assumptions and carry on. This patch does exactly that. In the case of length problems, the approach of "assume stated length is correct" is taken which means the offset might need adjusting. This is a relanding of b94191fe, fixing an LLD test and the LLDB build. Reviewed by: dblaikie, labath Differential Revision: https://reviews.llvm.org/D72158
2020-01-28 22:04:42 +08:00
# CHECK: error: undefined symbol: vtable for Foo
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: >>> {{.*}}:(.text+0x15)
[LLD][ELF] Follow the common pattern in a message about an undefined vtable symbol. In most cases, LLD prints its multiline diagnostic messages starting additional lines with ">>> ". That greatly helps external tools to parse the output, simplifying combining several lines of the log back into one message. The patch fixes the only message I found that does not follow the common pattern. Differential Revision: https://reviews.llvm.org/D77132
2020-03-31 18:36:23 +08:00
# CHECK-NEXT: >>> the vtable symbol may be undefined because the class is missing its key function (see https://lld.llvm.org/missingkeyfunction)
Add a doc for missing key function and an error message referencing the doc. Summary: This is a common error, and because many people don't know what the key function is, it is sometimes very confusing. The doc was originally written by Brooks Moses and slightly edited by me. Reviewers: MaskRay, espindola Subscribers: emaste, llvm-commits, arichardson Differential Revision: https://reviews.llvm.org/D55968 llvm-svn: 349941
2018-12-22 03:28:49 +08:00
clang+lld: Improve clang+ld.darwinnew.lld interaction, pass -demangle This patch: - adds an ld64.lld.darwinnew symlink for lld, to go with f2710d4b576, so that `clang -fuse-ld=lld.darwinnew` can be used to test new Mach-O lld while it's in bring-up. (The expectation is that we'll remove this again once new Mach-O lld is the defauld and only Mach-O lld.) - lets the clang driver know if the linker is lld (currently only triggered if `-fuse-ld=lld` or `-fuse-ld=lld.darwinnew` is passed). Currently only used for the next point, but could be used to implement other features that need close coordination between compiler and linker, e.g. having a diag for calling `clang++` instead of `clang` when link errors are caused by a missing C++ stdlib. - lets the clang driver pass `-demangle` to Mach-O lld (both old and new), in addition to ld64 - implements -demangle for new Mach-O lld - changes demangleItanium() to accept _Z, __Z, ___Z, ____Z prefixes (and updates one test added in D68014). Mach-O has an extra underscore for symbols, and the three (or, on Mach-O, four) underscores are used for block names. Differential Revision: https://reviews.llvm.org/D91884
2020-11-21 02:57:44 +08:00
# CHECK: error: undefined symbol: foo(int)
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: >>> {{.*}}:(.text+0x1A)
[LLD] Convert demangleItanium to use the higher level llvm::demangle function. NFC. This avoids a few lines of boilerplate of dealing with C string allocations. Add a testcase for a case where demangling shouldn't happen. Differential Revision: https://reviews.llvm.org/D68014 llvm-svn: 373076
2019-09-27 20:24:03 +08:00
[lld] Add support for other demanglers other than Itanium LLVM core library supports demangling other mangled symbols other than itanium, such as D and Rust. LLD should use those demanglers in order to output pretty demangled symbols on error messages. Reviewed By: MaskRay, #lld-macho Differential Revision: https://reviews.llvm.org/D116279
2022-01-05 11:05:10 +08:00
# CHECK: error: undefined symbol: Pi
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: >>> {{.*}}:(.text+0x1F)
# CHECK: error: undefined symbol: D main
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: >>> {{.*}}:(.text+0x24)
# CHECK: error: undefined symbol: a::main
# CHECK-NEXT: >>> referenced by undef.s
# CHECK-NEXT: >>> {{.*}}:(.text+0x29)
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: zed2
# CHECK-NEXT: >>> referenced by {{.*}}.o:(.text+0x0) in archive {{.*}}2.a
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: zed3
# CHECK-NEXT: >>> referenced by undef-debug.s:3 (dir{{/|\\}}undef-debug.s:3)
# CHECK-NEXT: >>> {{.*}}.o:(.text+0x0)
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: zed4
# CHECK-NEXT: >>> referenced by undef-debug.s:7 (dir{{/|\\}}undef-debug.s:7)
# CHECK-NEXT: >>> {{.*}}.o:(.text.1+0x0)
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: zed5
# CHECK-NEXT: >>> referenced by undef-debug.s:11 (dir{{/|\\}}undef-debug.s:11)
# CHECK-NEXT: >>> {{.*}}.o:(.text.2+0x0)
[ELF2] Add a new ELF linker based on the new PE/COFF linker. Differential Revision: http://reviews.llvm.org/D11188 llvm-svn: 243161
2015-07-25 05:03:07 +08:00
[ELF] Rework debug line parsing to use llvm::Error and callbacks (LLD-side) Reviewed by: ruiu, grimar, espindola Differential Revision: https://reviews.llvm.org/D44562 Summary: r331971 changes the debug line parser interface to report LLVM errors in an interface that different executables can use, rather than always being printed directly as warnings to stderr. This change allows LLD to make use of the new interface and call its own warning methods to report problems. llvm-svn: 331972
2018-05-10 18:52:21 +08:00
# Show that all line table problems are mentioned as soon as the object's line information
# is requested, even if that particular part of the line information is not currently required.
[test][ELF] Verify debug line corruption messages are printed once LLD warns if it encounters malformed debug data when parsing line information for an undefined reference. We only want to warn once. This patch adds additional checking to make sure the warnings are printed only once, both for variables within the same program and variables in later line programs. Reviewed by: grimar, MaskRay Differential Revision: https://reviews.llvm.org/D71759
2019-12-20 21:51:18 +08:00
# Also show that the warnings are only printed once.
[llvm/DWARFDebugLine] Fix a typo in one warning message
2020-06-11 19:04:26 +08:00
# CHECK: warning: unknown data in line table prologue at offset 0x00000000: parsing ended (at offset 0x00000037) before reaching the prologue end at offset 0x00000038
[lld] Fix test failure from d978656fd06 Tweak the test to account for the slightly different wording of the error message.
2020-03-02 18:28:48 +08:00
# CHECK-NEXT: warning: parsing line table prologue at offset 0x0000005b: unsupported version 1
[DebugInfo] Make most debug line prologue errors non-fatal to parsing Many of the debug line prologue errors are not inherently fatal. In most cases, we can make reasonable assumptions and carry on. This patch does exactly that. In the case of length problems, the approach of "assume stated length is correct" is taken which means the offset might need adjusting. This is a relanding of b94191fe, fixing an LLD test and the LLDB build. Reviewed by: dblaikie, labath Differential Revision: https://reviews.llvm.org/D72158
2020-01-28 22:04:42 +08:00
# CHECK-NEXT: warning: last sequence in debug line table at offset 0x00000061 is not terminated
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: zed6a
[DebugInfo] Make most debug line prologue errors non-fatal to parsing Many of the debug line prologue errors are not inherently fatal. In most cases, we can make reasonable assumptions and carry on. This patch does exactly that. In the case of length problems, the approach of "assume stated length is correct" is taken which means the offset might need adjusting. This is a relanding of b94191fe, fixing an LLD test and the LLDB build. Reviewed by: dblaikie, labath Differential Revision: https://reviews.llvm.org/D72158
2020-01-28 22:04:42 +08:00
# CHECK-NEXT: >>> referenced by undef-bad-debug.s:11 (dir{{/|\\}}undef-bad-debug.s:11)
# CHECK-NEXT: >>> {{.*}}4.o:(.text+0x0)
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK: error: undefined symbol: zed6b
[DebugInfo] Make most debug line prologue errors non-fatal to parsing Many of the debug line prologue errors are not inherently fatal. In most cases, we can make reasonable assumptions and carry on. This patch does exactly that. In the case of length problems, the approach of "assume stated length is correct" is taken which means the offset might need adjusting. This is a relanding of b94191fe, fixing an LLD test and the LLDB build. Reviewed by: dblaikie, labath Differential Revision: https://reviews.llvm.org/D72158
2020-01-28 22:04:42 +08:00
# CHECK-NEXT: >>> referenced by undef-bad-debug.s:21 (dir{{/|\\}}undef-bad-debug.s:21)
# CHECK-NEXT: >>> {{.*}}4.o:(.text+0x8)
# Show that a problem in a line table that prevents further parsing of that
# table means that no line information is displayed in the wardning.
# CHECK: error: undefined symbol: zed7
# CHECK-NEXT: >>> referenced by {{.*}}4.o:(.text+0x10)
[ELF] Prevent crash when reporting errors if debug line cannot be parsed LLD uses the debug info and debug line sections to determine the location of e.g. references to undefined symbols, when producing error messages. In the event that debug info was present, but debug line parsing failed for some reason, then a nullptr would end up being dereferenced by the location-lookup code. Differential Revision: https://reviews.llvm.org/D44205 Reviewers: grimar llvm-svn: 326899
2018-03-07 23:22:58 +08:00
[ELF] Rework debug line parsing to use llvm::Error and callbacks (LLD-side) Reviewed by: ruiu, grimar, espindola Differential Revision: https://reviews.llvm.org/D44562 Summary: r331971 changes the debug line parser interface to report LLVM errors in an interface that different executables can use, rather than always being printed directly as warnings to stderr. This change allows LLD to make use of the new interface and call its own warning methods to report problems. llvm-svn: 331972
2018-05-10 18:52:21 +08:00
# Show that a problem with one line table's information doesn't affect getting information from
# a different one in the same object.
[DebugInfo] Make most debug line prologue errors non-fatal to parsing Many of the debug line prologue errors are not inherently fatal. In most cases, we can make reasonable assumptions and carry on. This patch does exactly that. In the case of length problems, the approach of "assume stated length is correct" is taken which means the offset might need adjusting. This is a relanding of b94191fe, fixing an LLD test and the LLDB build. Reviewed by: dblaikie, labath Differential Revision: https://reviews.llvm.org/D72158
2020-01-28 22:04:42 +08:00
# CHECK: error: undefined symbol: zed8
[test][ELF] Use CHECK-NEXT to properly verify error messages Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D72092
2020-01-03 01:31:52 +08:00
# CHECK-NEXT: >>> referenced by undef-bad-debug2.s:11 (dir2{{/|\\}}undef-bad-debug2.s:11)
[DebugInfo] Make most debug line prologue errors non-fatal to parsing Many of the debug line prologue errors are not inherently fatal. In most cases, we can make reasonable assumptions and carry on. This patch does exactly that. In the case of length problems, the approach of "assume stated length is correct" is taken which means the offset might need adjusting. This is a relanding of b94191fe, fixing an LLD test and the LLDB build. Reviewed by: dblaikie, labath Differential Revision: https://reviews.llvm.org/D72158
2020-01-28 22:04:42 +08:00
# CHECK-NEXT: >>> {{.*}}tmp4.o:(.text+0x18)
[ELF] Rework debug line parsing to use llvm::Error and callbacks (LLD-side) Reviewed by: ruiu, grimar, espindola Differential Revision: https://reviews.llvm.org/D44562 Summary: r331971 changes the debug line parser interface to report LLVM errors in an interface that different executables can use, rather than always being printed directly as warnings to stderr. This change allows LLD to make use of the new interface and call its own warning methods to report problems. llvm-svn: 331972
2018-05-10 18:52:21 +08:00
[ELF][test] Change -o %t to -o /dev/null if the output is not needed
2020-02-13 13:48:45 +08:00
# RUN: not ld.lld %t.o %t2.a -o /dev/null -no-demangle 2>&1 | \
Demangle symbols in "undefined symbol" error message. llvm-svn: 281698
2016-09-16 11:52:45 +08:00
# RUN: FileCheck -check-prefix=NO-DEMANGLE %s
Change the error message format for undefined symbols. Previously, undefined symbol errors are one line like this and wasn't easy to read. /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' This patch make it more structured like this. bin/ld.lld: error: undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>> Writer.cpp.o in archive lib/liblldELF.a Discussion thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111459.html Differential Revision: https://reviews.llvm.org/D31481 llvm-svn: 299097
2017-03-31 03:13:47 +08:00
# NO-DEMANGLE: error: undefined symbol: _Z3fooi
[ELF] Better error reporting for undefined symbols This patch make lld show following details for undefined symbol errors: - file (line) - file (function name) - file (section name + offset) Differential revision: https://reviews.llvm.org/D25826 llvm-svn: 285186
2016-10-26 19:07:09 +08:00
.file "undef.s"
Demangle symbols in "undefined symbol" error message. llvm-svn: 281698
2016-09-16 11:52:45 +08:00
ELF: Report more than one undefined symbols if exist. http://reviews.llvm.org/D16643 llvm-svn: 259107
2016-01-29 06:56:29 +08:00
.globl _start
[ELF2] Add a new ELF linker based on the new PE/COFF linker. Differential Revision: http://reviews.llvm.org/D11188 llvm-svn: 243161
2015-07-25 05:03:07 +08:00
_start:
call foo
ELF: Report more than one undefined symbols if exist. http://reviews.llvm.org/D16643 llvm-svn: 259107
2016-01-29 06:56:29 +08:00
call bar
Print member name in undefined symbol error. llvm-svn: 268976
2016-05-10 05:40:06 +08:00
call zed1
Demangle symbols in "undefined symbol" error message. llvm-svn: 281698
2016-09-16 11:52:45 +08:00
call _Z3fooi
Add a doc for missing key function and an error message referencing the doc. Summary: This is a common error, and because many people don't know what the key function is, it is sometimes very confusing. The doc was originally written by Brooks Moses and slightly edited by me. Reviewers: MaskRay, espindola Subscribers: emaste, llvm-commits, arichardson Differential Revision: https://reviews.llvm.org/D55968 llvm-svn: 349941
2018-12-22 03:28:49 +08:00
call _ZTV3Foo
[LLD] Convert demangleItanium to use the higher level llvm::demangle function. NFC. This avoids a few lines of boilerplate of dealing with C string allocations. Add a testcase for a case where demangling shouldn't happen. Differential Revision: https://reviews.llvm.org/D68014 llvm-svn: 373076
2019-09-27 20:24:03 +08:00
call __Z3fooi
[lld] Add support for other demanglers other than Itanium LLVM core library supports demangling other mangled symbols other than itanium, such as D and Rust. LLD should use those demanglers in order to output pretty demangled symbols on error messages. Reviewed By: MaskRay, #lld-macho Differential Revision: https://reviews.llvm.org/D116279
2022-01-05 11:05:10 +08:00
call Pi
call _Dmain
call _RNvC1a4main