diff options
| author | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2016-04-17 06:42:30 +0000 |
|---|---|---|
| committer | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2016-04-17 06:42:30 +0000 |
| commit | 2c7cd4afaba59a2a80330df7adc02c8a4db7c5b9 (patch) | |
| tree | c08eb31c9fa90e0987906bbf91a1bbd358624e97 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py | |
| parent | c98ec20a0e31b6cf9b5c1f2c418d177d4661cdf5 (diff) | |
| download | bcm5719-llvm-2c7cd4afaba59a2a80330df7adc02c8a4db7c5b9.tar.gz bcm5719-llvm-2c7cd4afaba59a2a80330df7adc02c8a4db7c5b9.zip | |
IR: Fix type-refs in testcase from r266548
There's a hole in the verifier right now: if a module has no compile
units, it never checks that all the string-based DITypeRefs get
resolved. As a result, this testcase didn't fail the verifier, even
there were references to `!"has-uuid"` instead of `!"uuid"` (the former
was a composite type's 'name:' field, the latter its 'identifier:'
field).
I'm currently working on removing string-based type refs entirely, and
this testcase started failing (because the upgrade script can't resolve
the type refs). Rather than fixing the (about-to-be-removed) hole in
the verifier, I'm just going to fix the test so that my upgrade script
handles it.
llvm-svn: 266553
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
