On Fri, Feb 17, 2023 at 12:13:52PM +0100, Tobias Burnus wrote:
> Short version:
>
> This fixes potential and real bugs related to 'len=:' character variables
> as for the length/byte size an old/saved expression is used instead of
> the current value. - That's fine but not for allocatable/pointer with 'len=:'.
>
>
> Main part of the patch: Strip the SAVE_EXPR from the size expression:
>
> if (len && deferred && TREE_CODE (TYPE_SIZE (type)) == SAVE_EXPR)
> {
> gcc_assert (TREE_CODE (TYPE_SIZE_UNIT (type)) == SAVE_EXPR);
> TYPE_SIZE (type) = TREE_OPERAND (TYPE_SIZE (type), 0);
> TYPE_SIZE_UNIT (type) = TREE_OPERAND (TYPE_SIZE_UNIT (type), 0);
> }
>
>
> OK for mainline?
Short version: no.
>
> * * *
>
> Long version:
>
> BACKGROUND:
>
>
> (A) VLA / EXPLICIT-SIZE ARRAYS + LEN=<expr|var> STRINGS
>
>
> C knows something like VLA (variable length arrays), likewise Fortran
> knows explicit size array and character length where the length/size
> depends on an variable set before the current scoping unit. Examples:
>
> void f(int N)
> {
> int vla[N*5];
> }
>
> subroutine foo(n)
> integer :: n
> integer :: array(n*5)
> integer :: my_len
> ...
> my_len = 5
> block
> character(len=my_len, kind=4) :: str
>
> my_len = 99
> print *, len(str) ! still shows 5 - not 99
> end block
> end
Are you sure about the above comment? At the time
that str is declared, it is given a kind type parameter
of len=5 and kind=4. After changing my_len to 99
the kind type parameter of str does not change.
8.3 Automatic data objects
If a type parameter in a declaration-type-spec or in a char-length
in an entity-decl for a local variable of a subprogram or BLOCK
construct is defined by an expression that is not a constant
expression, the type parameter value is established on entry to a
procedure defined by the subprogram, or on execution of the BLOCK
statement, and is not affected by any redefinition or undefinition
of the variables in the expression during execution of the
procedure or BLOCK construct.
--
steve
