diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2020-02-01 10:02:20 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2020-02-01 10:02:20 +0100 |
| commit | add31061ec23e07fdf749dc335308efc81151a3d (patch) | |
| tree | b12aa90f1e67cd33d919ef010217f6dca5a995a9 /gcc/fortran/resolve.c | |
| parent | 2d33dcfe9f0494c9b56a8d704c3d27c5a4329ebc (diff) | |
| download | gcc-add31061ec23e07fdf749dc335308efc81151a3d.zip gcc-add31061ec23e07fdf749dc335308efc81151a3d.tar.gz gcc-add31061ec23e07fdf749dc335308efc81151a3d.tar.bz2 | |
fortran: Fix up TYPE_ARG_TYPES of procs with scalar VALUE optional args [PR92305]
The following patch fixes
-FAIL: libgomp.fortran/use_device_addr-1.f90 -O0 execution test
-FAIL: libgomp.fortran/use_device_addr-2.f90 -O0 execution test
that has been FAILing for several months on powerpc64le-linux.
The problem is in the Fortran FE, which adds the artificial arguments
for scalar VALUE OPTIONAL dummy args only to DECL_ARGUMENTS where the
current function can see them, but not to TYPE_ARG_TYPES; if those functions
aren't varargs, this confuses calls.c to pass the remaining arguments
(which aren't named (== not covered by TYPE_ARG_TYPES) and aren't varargs
either) in a different spot from what the callee (which has proper
DECL_ARGUMENTS for all args) expects. For the artificial length arguments
for character dummy args we already put them in both DECL_ARGUMENTS and
TYPE_ARG_TYPES.
2020-02-01 Jakub Jelinek <jakub@redhat.com>
PR fortran/92305
* trans-types.c (gfc_get_function_type): Also push boolean_type_node
types for non-character scalar VALUE optional dummy arguments.
* trans-decl.c (create_function_arglist): Skip those in
hidden_typelist. Formatting fix.
Diffstat (limited to 'gcc/fortran/resolve.c')
0 files changed, 0 insertions, 0 deletions