https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95998
Bug ID: 95998
Summary: gfc_typename use of static memory
Product: gcc
Version: unknown
Status: WAITING
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: tkoenig at gcc dot gnu.org
Target Milestone: ---
Status: WAITING
Last reconfirmed: 2020-07-08
Ever confirmed: 1
The comment in misc.c says it all...
/* Return a string describing the type and kind of a typespec. Because
we return alternating buffers, this subroutine can appear twice in
the argument list of a single statement. */
Did we really audit our code to make sure we keep to this restriction? :-|
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is static in C/C++ equivalent of SAVE in fortran (at least in the context of
gfc_typename)?
If yes, AFAIU the code the odd access to gfc_typename use buffer2, while even
ones
use buffer1? Wouldn't it be simple (safer?) to use only buffer1?
static char buffer[GFC_MAX_SYMBOL_LEN + 7]; /* 7 for "TYPE()" + '\0'. */
gfc_typespec *ts1;
gfc_charlen_t length = 0;
Same thing for gfc_dummy_typename, gfc_typename, ... .
