Hi Jakub,
This test FAILs because
f951: Error: '-mabi=ieeelongdouble' requires full ISA 2.06 support
compiler exited with status 1
FAIL: gfortran.dg/pr47614.f -O0 (test for excess errors)
As powerpc64le* only supports -mcpu=power8 and newer, I think we shouldn't
be testing with that option.
Ok for power-ieee128?
OK (I would also consider it obvious).
Though, I'm still unsure on what we should do with the array descriptors.
typedef struct dtype_type
{
size_t elem_len;
int version;
signed char rank;
signed char type;
signed short attribute;
}
dtype_type;
Is elem_len really element length, or kind, or both?
It is specified as a length, and should be set correctly also
for complex (where it is twice the length).
It seems a lot of code uses that interchangeably, is there anything where
we'd rely on whether it is the IBM extended real(kind=16) or IEEE quad
real(kind=16) (either in libgfortran or elsewhere)?
I think we use sizeof in all relevant files.
At least in libgfortran/generates/*, GFC_DESCRIPTOR_SIZE is mostly used
as mask_kind (I think the mask arrays are always logical not real/complex,
right?), or for logical stuff like matmul_l*.
Yes, masks are always of type logical, so that should not be an issue.
There are two direct uses of elem_len in caf/singe.c, one in
date_and_time.c and one in io/transfer.c. There is also some
use of a variable of that name ISO_Fortran_binding.c, which can
be checked later.
Best regards
Thomas
