[PATCH][gdb/testsuite] Fix gdb.ada/float-bits.exp with -m32

[Tom de Vries]

On 4/25/22 12:31, Luis Machado wrote:
> On 4/14/22 14:14, Tom de Vries via Gdb-patches wrote:
>> Hi,
>>
>> With test-case gdb.ada/float-bits.exp and native we get:
>> ...
>> (gdb) print 16llf#7FFFF7FF4054A56FA5B99019A5C8#^M
>> $9 = 5.0e+25^M
>> (gdb) PASS: gdb.ada/float-bits.exp: print 
>> 16llf#7FFFF7FF4054A56FA5B99019A5C8#
>> ...
>> but with target board unix/-m32 we have instead:
>> ...
>> (gdb) print 16llf#7FFFF7FF4054A56FA5B99019A5C8#^M
>> Cannot export value 2596145952482202326224873165792712 as 96-bits \
>>    unsigned integer (must be between 0 and 
>> 79228162514264337593543950335)^M
>> (gdb) FAIL: gdb.ada/float-bits.exp: print 
>> 16llf#7FFFF7FF4054A56FA5B99019A5C8#
>> ...
>>
>> Fix this by testing whether 16llf is supported by doing ptype 
>> long_long_float
>> which gets us either:
>> ...
>> type = <16-byte float>^M
>> ...
>> or:
>> ...
>> type = <12-byte float>^M
>> ...
>>
>> Tested on x86_64-linux with native and unix/-m32.
> 
> Unfortunately not all targets support 128-bit long doubles. For arm and 
> aarch64 the compiler won't generate a 128-bit float, but a 64-bit float, 
> so the 16ll tests won't be meaningful.
> 

Right, but I'd expect those tests are skipped because 16llf_supported is 
0 for 64-bit long double.

> FAIL: gdb.ada/float-bits.exp: print val_long_double
> FAIL: gdb.ada/float-bits.exp: print val_long_double after assignment
> 

Can you show me the actual failure mode, that is, copy from gdb.log 
instead of gdb.sum?  I'm surprised that these fail because AFAICT, the 
used constant: 5.0e+25 is exactly representable in 64-bit ieee ( I used 
https://babbage.cs.qc.cuny.edu/ieee-754.old/decimal.html to check this ).

> I wonder if it would be best to bail out as soon as we find out the 
> target has no support for 128-bit floats. I can write a patch for that.
> 

With a rewrite like this:
...
-set 16llf_supported 0
+set long_double_bytes 0
  gdb_test_multiple "ptype long_long_float" "" {
-    -re -wrap "<16-byte float>" {
-       set 16llf_supported 1
-       pass $gdb_test_name
-    }
-    -re -wrap "<\\d+-byte float>" {
-       pass $gdb_test_name
+    -re -wrap "<\(\\d+\)-byte float>" {
+       set long_double_bytes $expect_out(1,string)
      }
  }

+set 16llf_supported [expr $long_double_bytes >= 16]
...
we can formulate the precondition for any test in terms number of long 
double bytes.

Thanks,
- Tom

> I'm guessing some 16ll tests still work for 12-byte floats, right?
> 
> What do you think?