Please use GitHub pull requests for new patches. Avoid migrating existing patches. Phabricator shutdown timeline
Changeset View
Changeset View
Standalone View
Standalone View
test/tools/llvm-symbolizer/sym.test
| Show All 16 Lines | |||||
| # | # | ||||
| #Build as : clang -g -O2 addr.c | #Build as : clang -g -O2 addr.c | ||||
| RUN: llvm-symbolizer -print-address -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck %s | RUN: llvm-symbolizer -print-address -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck %s | ||||
| RUN: llvm-symbolizer -addresses -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck %s | RUN: llvm-symbolizer -addresses -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck %s | ||||
| RUN: llvm-symbolizer -a -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck %s | RUN: llvm-symbolizer -a -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck %s | ||||
| RUN: llvm-symbolizer -inlining -print-address -pretty-print -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | RUN: llvm-symbolizer -inlining -print-address -pretty-print -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | ||||
| RUN: llvm-symbolizer -inlining -print-address -p -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | RUN: llvm-symbolizer -inlining -print-address -p -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | ||||
| RUN: llvm-symbolizer -inlines -print-address -pretty-print -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | |||||
| RUN: llvm-symbolizer -inlines -print-address -p -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | |||||
Quolyk: One more nit. This file contains redundant tests. coff-exports.test tests are already covered… | |||||
Not Done ReplyInline ActionsI'm not too bothered by this either way. In an ideal world, we would actually have a test dedicated to --inlining and its aliases, rather than adding them here, but I don't know if there's a huge benefit to doing that. @dyung, if you're happy enough writing such a test, it might be worthwhile. jhenderson: I'm not too bothered by this either way. In an ideal world, we would actually have a test… | |||||
| RUN: llvm-symbolizer -i -print-address -pretty-print -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | |||||
| RUN: llvm-symbolizer -i -print-address -p -obj=%p/Inputs/addr.exe < %p/Inputs/addr.inp | FileCheck -check-prefix="PRETTY" %s | |||||
| RUN: echo "0x1" > %t.input | RUN: echo "0x1" > %t.input | ||||
| RUN: llvm-symbolizer -obj=%p/Inputs/zero < %t.input | FileCheck -check-prefix="ZERO" %s | RUN: llvm-symbolizer -obj=%p/Inputs/zero < %t.input | FileCheck -check-prefix="ZERO" %s | ||||
| #CHECK: some text | #CHECK: some text | ||||
| #CHECK: 0x40054d | #CHECK: 0x40054d | ||||
| #CHECK: main | #CHECK: main | ||||
| #CHECK: {{[/\]+}}tmp{{[/\]+}}x.c:14:0 | #CHECK: {{[/\]+}}tmp{{[/\]+}}x.c:14:0 | ||||
| #CHECK: some text2 | #CHECK: some text2 | ||||
| Show All 9 Lines | |||||
One more nit. This file contains redundant tests. coff-exports.test tests are already covered in coff-dwarf.test. On the one hand the more tests the better, on the other hand they test the same thing. @jhenderson is more confident, I suggest him to clarify this. Probably you have opinion on that.