There's 8 consistent failures in this test that show up in both GCC 4.7 and Clang. Rather than trying to diagnose whether these are GDB test suite bugs or bugs across both compilers. In any case this doesn't seem to represent a case where Clang is lagging behind.
(it's also possible that I've done something wrong in the way these tests are executed & it should be passing with GCC)
| | |
| --- | --- |
| Bugzilla Link | [14605](https://llvm.org/bz14605) |
| Version | unspecified |
| OS | All |
| Blocks | llvm/llvm-project#14767 |
| CC | @DougGregor,@echristo |
## Extended Description
There's 8 consistent failures in this test that show up in both GCC 4.7 and Clang. Rather than trying to diagnose whether these are GDB test suite bugs or bugs across both compilers. In any case this doesn't seem to represent a case where Clang is lagging behind.
(it's also possible that I've done something wrong in the way these tests are executed & it should be passing with GCC)
Disabled in r170181
Extended Description
There's 8 consistent failures in this test that show up in both GCC 4.7 and Clang. Rather than trying to diagnose whether these are GDB test suite bugs or bugs across both compilers. In any case this doesn't seem to represent a case where Clang is lagging behind.
(it's also possible that I've done something wrong in the way these tests are executed & it should be passing with GCC)
Disabled in r170181