mirror of
https://gcc.gnu.org/git/gcc.git
synced 2024-11-23 19:03:59 +08:00
4e5ca7ff8c
The boz_15.f90 test FAILs on powerpc64le-linux when -mabi=ieeelongdouble
is used (either default through --with-long-double-format=ieee or
when used explicitly).
The problem is that the read/write transfer routines are called with
BT_REAL (or BT_COMPLEX) type and kind 17 which is magic we use to say
it is the IEEE quad real(kind=16) rather than the IBM double double
real(kind=16). For the floating point input/output we then handle kind
17 specially, but for B/O/Z we just treat the bytes of the floating point
value as binary blob and using 17 in that case results in unexpected
behavior, for write it means we don't estimate right how many chars we'll
need and print ******************** etc. rather than what we should, and
even with explicit size we'd print one further byte than intended.
For read it would even mean overwriting some unrelated byte after the
floating point object.
Fixed by using 16 instead of 17 in the read_radix and write_{b,o,z} calls.
2022-08-01 Jakub Jelinek <jakub@redhat.com>
PR libfortran/106079
* io/transfer.c (formatted_transfer_scalar_read,
formatted_transfer_scalar_write): For type BT_REAL with kind 17
change kind to 16 before calling read_radix or write_{b,o,z}.
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| async.c | ||
| async.h | ||
| close.c | ||
| fbuf.c | ||
| fbuf.h | ||
| file_pos.c | ||
| format.c | ||
| format.h | ||
| inquire.c | ||
| intrinsics.c | ||
| io.h | ||
| list_read.c | ||
| lock.c | ||
| open.c | ||
| read.c | ||
| size_from_kind.c | ||
| transfer128.c | ||
| transfer.c | ||
| unit.c | ||
| unix.c | ||
| unix.h | ||
| write_float.def | ||
| write.c | ||