Open Quuxplusone opened 6 years ago
Bugzilla Link | PR35062 |
Status | NEW |
Importance | P enhancement |
Reported by | Davide Italiano (ditaliano@apple.com) |
Reported on | 2017-10-24 11:10:54 -0700 |
Last modified on | 2018-03-15 06:14:12 -0700 |
Version | unspecified |
Hardware | PC Windows NT |
CC | jan@jankratochvil.net, llvm-bugs@lists.llvm.org, tschelle@redhat.com, tstellar@redhat.com |
Fixed by commit(s) | |
Attachments | |
Blocks | |
Blocked by | |
See also |
Test results on Fedora 27 with GCC 7.3.1, trunk r327484, static build with the
CMake invocation below:
cmake ../llvm -G Ninja -DCMAKE_BUILD_TYPE=Release '-
DLLVM_ENABLE_PROJECTS=clang;lldb' -DCMAKE_C_COMPILER=/usr/bin/gcc -
DCMAKE_CXX_COMPILER=/usr/bin/g++ -DLLVM_TARGETS_TO_BUILD=X86
=============
Issue Details
=============
FAIL: test_more_expr_commands_dwarf (expression_command/test/TestExprs2.py)
FAIL: test_more_expr_commands_dwo (expression_command/test/TestExprs2.py)
FAIL: test_more_expr_commands_gmodules (expression_command/test/TestExprs2.py)
ERROR: test_with_run_command_dwarf (functionalities/data-formatter/data-
formatter-stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_dwarf (functionalities/data-formatter/data-
formatter-stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: test_with_run_command_dwo (functionalities/data-formatter/data-formatter-
stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_dwo (functionalities/data-formatter/data-formatter-
stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: test_with_run_command_gmodules (functionalities/data-formatter/data-
formatter-stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_gmodules (functionalities/data-formatter/data-
formatter-stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: [EXCEPTIONAL EXIT 11 (SIGSEGV)] test_mips_n32
(functionalities/postmortem/elf-core/TestLinuxCore.py)
UNEXPECTED SUCCESS: test (functionalities/register/intel_avx/TestYMMRegister.py)
UNEXPECTED SUCCESS: test_dwarf
(functionalities/thread/exit_during_break/TestExitDuringBreak.py)
UNEXPECTED SUCCESS: test_dwo
(functionalities/thread/exit_during_break/TestExitDuringBreak.py)
UNEXPECTED SUCCESS: test_gmodules
(functionalities/thread/exit_during_break/TestExitDuringBreak.py)
UNEXPECTED SUCCESS: test_lldbmi_gdb_set_target_async_off (tools/lldb-
mi/TestMiGdbSetShow.py)
UNEXPECTED SUCCESS: test_lldbmi_process_output (tools/lldb-
mi/syntax/TestMiSyntax.py)
UNEXPECTED SUCCESS: test_lldbmi_settings_set_target_run_args_after (tools/lldb-
mi/interpreter/TestMiInterpreterExec.py)
UNEXPECTED SUCCESS: test_process_interrupt_gmodules
(functionalities/thread/state/TestThreadStates.py)
UNEXPECTED SUCCESS: test_sb_api_listener_resume
(api/multithreaded/TestMultithreaded.py)
UNEXPECTED SUCCESS: test_with_dwarf (lang/cpp/printf/TestPrintf.py)
UNEXPECTED SUCCESS: test_with_dwo (lang/cpp/printf/TestPrintf.py)
UNEXPECTED SUCCESS: test_with_gmodules (lang/cpp/printf/TestPrintf.py)
===================
Test Result Summary
===================
Test Methods: 2655
Reruns: 0
Success: 1671
Expected Failure: 146
Failure: 3
Error: 6
Exceptional Exit: 1
Unexpected Success: 12
Skip: 816
Timeout: 0
Expected Timeout: 0
Tillmann, if you're interested at looking at them, I may provide guidance.
Please note that very few people tried compilers different from clang
ToT, so one of the reasons why this fails is because the debug informations emitted are different. Hard to say.
If I was somebody looking at this, I'd start with getting the full testsuite passing on Fedora with the in-tree clang (checkout clang in llvm/tools and, presumably, libcxx in projects/). At that point you have a baseline and can compare with other compilers.
For reference, we're able to get a fairly green testsuite on MacOS these days (although it took a lot of effort and energy to get there).
Thanks for the feedback Davide. I agree that having a Clang-based baseline is the best way forward. I've noticed the steady improvements regarding the LLDB test suite and it seems there is not too much missing to actually get Linux fully green :)
I noticed that the results above that I pasted yesterday were actually using the corresponding trunk Clang. I did the build with the monorepo and it seems the LLDB test suite picks the in-tree Clang by default (even when LLVM/Clang/LLDB are built with GCC). Based on https://lldb.llvm.org/test.html I was assuming that it will use the same compiler that is used for building LLDB.
Will paste GCC vs Clang results of today's trunk build shortly.
Test results on Fedora 27 with GCC 7.3.1, trunk r327610, static build with the
CMake invocation below:
cmake ../llvm -G Ninja -DCMAKE_BUILD_TYPE=Release '-
DLLVM_ENABLE_PROJECTS=clang;lldb' -DCMAKE_C_COMPILER=/usr/bin/gcc -
DCMAKE_CXX_COMPILER=/usr/bin/g++ -DLLVM_TARGETS_TO_BUILD=X86
(Unexpected success results removed to decrease noise)
Clang r327610:
=============
Issue Details
=============
FAIL: test_more_expr_commands_dwarf (expression_command/test/TestExprs2.py)
FAIL: test_more_expr_commands_dwo (expression_command/test/TestExprs2.py)
FAIL: test_more_expr_commands_gmodules (expression_command/test/TestExprs2.py)
FAIL: test_source_map (functionalities/source-map/TestTargetSourceMap.py)
ERROR: test_with_run_command_dwarf (functionalities/data-formatter/data-
formatter-stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_dwarf (functionalities/data-formatter/data-
formatter-stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: test_with_run_command_dwo (functionalities/data-formatter/data-formatter-
stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_dwo (functionalities/data-formatter/data-formatter-
stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: test_with_run_command_gmodules (functionalities/data-formatter/data-
formatter-stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_gmodules (functionalities/data-formatter/data-
formatter-stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: [EXCEPTIONAL EXIT 11 (SIGSEGV)] test_mips_n32
(functionalities/postmortem/elf-core/TestLinuxCore.py)
===================
Test Result Summary
===================
Test Methods: 2643
Reruns: 0
Success: 1663
Expected Failure: 140
Failure: 4
Error: 6
Exceptional Exit: 1
Unexpected Success: 10
Skip: 819
Timeout: 0
Expected Timeout: 0
GCC 7.3.1:
=============
Issue Details
=============
FAIL: test_guess_language (functionalities/frame-language/TestGuessLanguage.py)
FAIL: test_integer_args_dwarf (lang/cpp/template/TestTemplateArgs.py)
FAIL: test_integer_args_dwo (lang/cpp/template/TestTemplateArgs.py)
FAIL: test_more_expr_commands_dwarf (expression_command/test/TestExprs2.py)
FAIL: test_more_expr_commands_dwo (expression_command/test/TestExprs2.py)
FAIL: test_source_map (functionalities/source-map/TestTargetSourceMap.py)
FAIL: test_with_dwarf (lang/c/inlines/TestRedefinitionsInInlines.py)
FAIL: test_with_dwo (lang/c/inlines/TestRedefinitionsInInlines.py)
ERROR: test_mpx_boundary_violation_dwarf
(functionalities/register/intel_xtended_registers/mpx_bound_violation/TestBoundViolation.py)
ERROR: test_mpx_boundary_violation_dwo
(functionalities/register/intel_xtended_registers/mpx_bound_violation/TestBoundViolation.py)
ERROR: test_mpx_registers_with_example_code_dwarf
(functionalities/register/intel_xtended_registers/TestMPXRegisters.py)
ERROR: test_mpx_registers_with_example_code_dwo
(functionalities/register/intel_xtended_registers/TestMPXRegisters.py)
ERROR: test_with_run_command_dwarf (functionalities/data-formatter/data-
formatter-stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_dwarf (functionalities/data-formatter/data-
formatter-stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: test_with_run_command_dwo (functionalities/data-formatter/data-formatter-
stl/libstdcpp/smart_ptr/TestDataFormatterStdSmartPtr.py)
ERROR: test_with_run_command_dwo (functionalities/data-formatter/data-formatter-
stl/libstdcpp/unique_ptr/TestDataFormatterStdUniquePtr.py)
ERROR: [EXCEPTIONAL EXIT 11 (SIGSEGV)] test_mips_n32
(functionalities/postmortem/elf-core/TestLinuxCore.py)
===================
Test Result Summary
===================
Test Methods: 1974
Reruns: 0
Success: 1219
Expected Failure: 106
Failure: 8
Error: 8
Exceptional Exit: 1
Unexpected Success: 14
Skip: 618
Timeout: 0
Expected Timeout: 0