https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
--- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to anlauf from comment #18)
> Tentative patch, regtests cleanly but otherwise untested:
>
> diff --git a/gcc/fortran/trans-expr.cc b/gcc/fortran/trans-expr.cc
> index 850007fd2e1..0a1520e95ba 100644
> --- a/gcc/fortran/trans-expr.cc
> +++ b/gcc/fortran/trans-expr.cc
> @@ -6503,8 +6503,19 @@ gfc_conv_procedure_call (gfc_se * se, gfc_symbol *
> sym,
> else
> {
> bool add_clobber;
> - add_clobber = fsym && fsym->attr.intent == INTENT_OUT
> - && !fsym->attr.allocatable && !fsym->attr.pointer
> + gfc_symbol *dsym = fsym;
> + gfc_dummy_arg *dummy;
> +
> + /* Use associated dummy as fallback for formal
> + argument if there is no explicit interface. */
> + if (dsym == NULL
> + && (dummy = arg->associated_dummy)
> + && dummy->intrinsicness ==
> GFC_NON_INTRINSIC_DUMMY_ARG
> + && dummy->u.non_intrinsic->sym)
> + dsym = dummy->u.non_intrinsic->sym;
> +
> + add_clobber = dsym && dsym->attr.intent == INTENT_OUT
> + && !dsym->attr.allocatable && !dsym->attr.pointer
> && e->symtree && e->symtree->n.sym
> && !e->symtree->n.sym->attr.dimension
> && !e->symtree->n.sym->attr.pointer
>
> Does this fix the remaining issue?
>
> What is the best way to write a testcase that checks that the clobber is
> inserted properly?
For the testcase in comment#8 you could do
! { dg-do compile }
! { dg-options "-fdump-tree-original" }
module error_function
integer, parameter :: r8 = selected_real_kind(12) ! 8 byte real
contains
SUBROUTINE CALERF_r8(ARG, RESULT, JINT)
integer, parameter :: rk = r8
real(rk), intent(in) :: arg
real(rk), intent(out) :: result
IF (Y .LE. THRESH) THEN
END IF
end SUBROUTINE CALERF_r8
FUNCTION DERFC(X)
integer, parameter :: rk = r8 ! 8 byte real
real(rk), intent(in) :: X
real(rk) :: DERFC
CALL CALERF_r8(X, DERFC, JINT)
END FUNCTION DERFC
end module error_function
! { dg-final { scan-tree-dump-not "derfc = {CLOBBER};" } }
tough a more precise test would be to use scan-tree-dump-times "CLOBBER" 1
and scan-tree-dump "__result_derfc = {CLOBBER};". With the bug we see
__attribute__((fn spec (". r ")))
real(kind=8) derfc (real(kind=8) & restrict x)
{
integer(kind=4) jint;
real(kind=8) __result_derfc;
derfc = {CLOBBER};
calerf_r8 ((real(kind=8) *) x, &__result_derfc, &jint);
return __result_derfc;
and corrected there should be either
__result_derfc = {CLOBBER};
instead or the clobber not emitted (for a missed optimization only).
