https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97082
--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Ian Lance Taylor from comment #2) > Does btest pass? It's hard to see why mtest would fail if btest passes. current results [darwin16, darwin19] are: PASS: allocfail.sh PASS: test_elf_32 PASS: test_elf_64 PASS: test_macho PASS: test_xcoff_32 PASS: test_xcoff_64 PASS: test_pecoff PASS: test_unknown PASS: unittest PASS: unittest_alloc FAIL: btest FAIL: btest_alloc PASS: stest PASS: stest_alloc PASS: edtest PASS: edtest_alloc PASS: ttest PASS: ttest_alloc FAIL: dwarf5 FAIL: dwarf5_alloc FAIL: mtest the reason for btest* and mtest fails is unknown at present. Most likely the fails for dwarf5 would relate to whether dsymutil is yet 'dwarf5 aware' .. I believe the debug default for the system toolchain(s) is dwarf4. Using the most recent command line tools (XC12 beta5) on darwin19, dsymutil actually aborts with the dwarf5 input.
