diff options
| author | Andreas Arnez <arnez@linux.vnet.ibm.com> | 2018-01-18 19:41:16 +0100 |
|---|---|---|
| committer | Andreas Arnez <arnez@linux.vnet.ibm.com> | 2018-01-18 19:41:16 +0100 |
| commit | 25d4fd80936744adfa49f133524e3f342604a1cb (patch) | |
| tree | 878434010509f259b0306fe6326774246b2e798d /gdb/symfile-debug.c | |
| parent | 4a17f7688fbab8f170144fa13ffcd06bc749e6ec (diff) | |
| download | gdb-25d4fd80936744adfa49f133524e3f342604a1cb.zip gdb-25d4fd80936744adfa49f133524e3f342604a1cb.tar.gz gdb-25d4fd80936744adfa49f133524e3f342604a1cb.tar.bz2 | |
S390: Use soft float in s390-tdbregs test case
The GDB test case s390-tdbregs.exp verifies GDB's handling of the
"transaction diagnostic block". For simplicity, the test case uses the
"transaction begin" (TBEGIN) instruction with the "allow floating-point
operation" flag set to zero. But some GCC versions may indeed emit
floating point or vector instructions for this test case. If this happens
in the transaction, it aborts, and an endless loop results.
This change tells the compiler to produce a soft-float binary, so no
floating-point or vector registers are touched.
gdb/testsuite/ChangeLog:
* gdb.arch/s390-tdbregs.exp: Add the compile option -msoft-float.
Diffstat (limited to 'gdb/symfile-debug.c')
0 files changed, 0 insertions, 0 deletions