[Bug fortran/98010] [OpenACC] 'gcc/fortran/options.c:gfc_post_options' should consider 'flag_openacc' in addition to 'flag_openmp'?

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98010

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <bur...@gcc.gnu.org>:

https://gcc.gnu.org/g:f4e7ea81d1369d4d6cb6d8e440aefb3407142e05

commit r11-5571-gf4e7ea81d1369d4d6cb6d8e440aefb3407142e05
Author: Tobias Burnus <tob...@codesourcery.com>
Date:   Mon Nov 30 15:27:44 2020 +0100

    Fortran: -fno-automatic and -fopenacc / recusion check cleanup

    Options: -fopenmp and -fopenacc imply concurrent calls to a
    procedure; now also -fopenacc implies -frecursive, disabling
    that larger local const-size array variables use static memory.

    Run-time recursion check: Always reset the check variable at the
    end of the procedure; this avoids a bogus error with -fopenmp
    when called twice nonconcurrently/nonrecursively. (Issue requires
    using -fno-automatic or -fmax-stack-var-size= to trigger.)

    gcc/fortran/ChangeLog:

            PR fortran/98010
            PR fortran/98013
            * options.c (gfc_post_options): Also imply recursive with
            -fopenacc.
            * trans-decl.c (gfc_generate_function_code): Simplify condition.