diff options
| author | Pedro Alves <palves@redhat.com> | 2015-03-09 17:47:18 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-03-09 17:47:18 +0000 |
| commit | b2df3cefb124e3cab3a4bf0ba2f25fe8e1d25283 (patch) | |
| tree | 585995f23429708d7d3b0f988f9e2d113dc5df71 /gdb/testsuite/gdb.dwarf2/dw2-reg-undefined.S | |
| parent | ef878e5310ed154450b84cdedd4dd248c7697a2c (diff) | |
| download | gdb-b2df3cefb124e3cab3a4bf0ba2f25fe8e1d25283.zip gdb-b2df3cefb124e3cab3a4bf0ba2f25fe8e1d25283.tar.gz gdb-b2df3cefb124e3cab3a4bf0ba2f25fe8e1d25283.tar.bz2 | |
Delete gdb/testsuite/dg-extract-results.py
Unfortunately, the Python version of the dg-extract-results.sh script
doesn't produce stable-enough results for GDB. The test messages
appear to end up alpha sorted (losing the original sequence) and also
sorting changes between runs for some reason. That may be tolerable
for GCC, but for GDB, it often renders test results diffing between
different revisions unworkable.
Until that is fixed upstream, delete the script from the GDB tree.
testsuite/ChangeLog:
2015-03-09 Pedro Alves <palves@redhat.com>
* dg-extract-results.py: Delete.
Diffstat (limited to 'gdb/testsuite/gdb.dwarf2/dw2-reg-undefined.S')
0 files changed, 0 insertions, 0 deletions