[Bug fortran/103662] [12 Regression] TBAA problem in Fortran FE triggering in gfortran.dg/unlimited_polymorphic_3.f03

[cvs-commit at gcc dot gnu.org]

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

--- Comment #23 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:22c24ba48a20a4944a50cca06449debed7d1b3f4

commit r12-8260-g22c24ba48a20a4944a50cca06449debed7d1b3f4
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Apr 26 09:17:32 2022 +0200

    testsuite: Improve unlimited_polymorphic_3.f03 [PR103662]

    On Mon, Apr 25, 2022 at 01:38:25PM +0200, Mikael Morin wrote:
    > I have just pushed the attached fix for two UNRESOLVED checks at -O0 that
I
    > hadnât seen.

    I don't like forcing of DSE in -O0 compilation, wouldn't it be better
    to just not check the dse dump at -O0 like in the following patch?

    Even better would be to check that the z._data = stores are both present
    in *.optimized dump, but that doesn't really work at -O2 or above because
    we inline the functions and optimize it completely away (both the stores
    and corresponding reads).

    The first hunk is needed so that __OPTIMIZE__ effective target works in
    Fortran testsuite, otherwise one gets a pedantic error and __OPTIMIZE__
    is considered not to match at all.

    2022-04-26  Jakub Jelinek  <jakub@redhat.com>

            PR fortran/103662
            * lib/target-supports.exp (check_effective_target___OPTIMIZE__):
Add
            a var definition to avoid pedwarn about empty translation unit.
            * gfortran.dg/unlimited_polymorphic_3.f03: Remove -ftree-dse from
            dg-additional-options, guard scan-tree-dump-not directives on
            __OPTIMIZE__ target.