From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [r13-2446 Regression] FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for excess errors) on Linux/x86_64
Date: Tue, 6 Sep 2022 09:49:12 +0200 [thread overview]
Message-ID: <Yxb7eM1nz0LvdeB0@tucnak> (raw)
In-Reply-To: <202209052354.285Ns5071120234@shliclel314.sh.intel.com>
On Tue, Sep 06, 2022 at 07:54:05AM +0800, haochen.jiang via Gcc-patches wrote:
> On Linux/x86_64,
>
> 938cda536019cd6a1bc0dd2346381185b420bbf8 is the first bad commit
> commit 938cda536019cd6a1bc0dd2346381185b420bbf8
> Author: Tobias Burnus <tobias@codesourcery.com>
> Date: Mon Sep 5 18:05:24 2022 +0200
>
> Fortran/openmp: Partial OpenMP 5.2 doacross and omp_cur_iteration support
>
> caused
>
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 28)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 42)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 48)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 55)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 70)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for errors, line 82)
> FAIL: gfortran.dg/gomp/doacross-5.f90 -O (test for excess errors)
Seems this is still being diagnosed in the FE when it should be deferred to
the middle-end now (only when we find out if it is doacross or not).
If you really want to diagnose it in the FE (and do the doacross discovery
there too), I think the testcase needs to be split into 2, because the FE
errors apparently result in the gimplifier or omp lowering not being done
at all.
Jakub
next prev parent reply other threads:[~2022-09-06 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 23:54 haochen.jiang
2022-09-06 7:49 ` Jakub Jelinek [this message]
2022-09-06 8:12 ` Tobias Burnus
2022-09-06 8:24 ` Jakub Jelinek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yxb7eM1nz0LvdeB0@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).