https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85063
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So just make it a file scope static var instead, instead of disabling the
optimization?
Aren't there many other cases where static vars can be introduced, e.g. in the
gimplifier when gimplifying initializers, compound literals, ...?
What about switch inside of OpenACC constructs?
Is there any reason why function static vars can't be supported, besides that
the standard says they aren't allowed? The diagnostics should be done in the
FE anyway, or could be guarded with !DECL_ARTIFICIAL etc.
