Although we build the library with GCC which is known to support
_Static_assert this might be done on a system without the macro
mapping static_assert to the compiler keyword.
The use of static_assert introduced with r12-6126-g3430132f3e82
causes bootstrap to fail on such targets, fixed by using t
Hi!
The following patch quiets
../../../libgfortran/generated/in_pack_r17.c:35:1: warning: no previous
prototype for ‘internal_pack_r17’ [-Wmissing-prototypes]
../../../libgfortran/generated/in_pack_c17.c:35:1: warning: no previous
prototype for ‘internal_pack_c17’ [-Wmissing-prototypes]
../../.
Hi!
The following patch detects the powerpc64le-linux kind == 16 cases
and for the -mabi=ieeelongdouble case (no matter whether it is the
configured in default or just option used on the command line) uses
_r17 or _c17 instead of _r16 or _c17 in the library API names.
>From what I can see, e.g. c
On Fri, Dec 31, 2021 at 03:16:47PM +0100, Jakub Jelinek via Gcc-patches wrote:
> Haven't played enough with it to see if the various *_r17 or *_c17
> API entrypoints are called (but verified abi_kind is right in the
> debugger), in all my attempts so far everything was emitted inline.
Actually pla
Hi Jakub,
Ok for power-ieee128 branch?
OK. Thanks for stepping up! I am a little distracted right now, but
I think I will also continue working on this for a bit.
Best regards
Thomas
Hi Jakub,
Actually playing with that (e.g. for matmul) revealed a brown paper bag
bug in the previous patch, fixed thusly:
OK.
Thanks a lot!
Best regards
Thomas
Attached patch pushed as cb48166e52c0f159eb80a0666c4847825e294ec0
Confirmed by Dave to make the testcase pass on hppa-unknown-linux-gnu
FX
0001-Fortran-Fix-test-on-targets-without-REAL128.patch
Description: Binary data
