From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>,
gcc-regression@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>,
haochen.jiang@intel.com
Subject: Re: [r14-1579 Regression] FAIL: gfortran.dg/gomp/target-update-1.f90 -O scan-tree-dump gimple "#pragma omp target update to\\(c \\[len: [0-9]+\\]\\) to\\(present:a \\[len: [0-9]+\\]\\) to\\(e \\[len: [0-9]+\\]\\) from\\(present:b \\[len: [0-9]+\\]\\) from\\(d \\[len: [0-9]+\\]\\)" on Linux/x86_64
Date: Wed, 7 Jun 2023 11:13:11 +0400 [thread overview]
Message-ID: <CAF06A8C-656E-4A1D-80BD-6F0BC0BDA4B0@linaro.org> (raw)
In-Reply-To: <202306062250.356Mo6Qw3100125@shliclel4214.sh.intel.com>
Hi Tobias,
We are also seeing this failure on arm-linux-gnueabihf.
It seems the problem is different order of variables in output:
- c a e d b
versus expected
- c a e b d
This is tree-dump output on arm-linux-gnueabihf:
#pragma omp target update to(c [len: 4]) to(present:a [len: 4000]) to(e [len: 4]) from(d [len: 4]) from(present:b [len: 4000])
Let me know if you need any help in troubleshooting this.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jun 7, 2023, at 02:50, haochen.jiang via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> On Linux/x86_64,
>
> 4ede915d5dde935a16df2c6640aee5ab22348d30 is the first bad commit
> commit 4ede915d5dde935a16df2c6640aee5ab22348d30
> Author: Tobias Burnus <tobias@codesourcery.com>
> Date: Tue Jun 6 16:47:16 2023 +0200
>
> openmp: Add support for the 'present' modifier
>
> caused
>
> FAIL: gfortran.dg/gomp/target-update-1.f90 -O scan-tree-dump gimple "#pragma omp target update to\\(c \\[len: [0-9]+\\]\\) to\\(present:a \\[len: [0-9]+\\]\\) to\\(e \\[len: [0-9]+\\]\\) from\\(present:b \\[len: [0-9]+\\]\\) from\\(d \\[len: [0-9]+\\]\\)"
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-1579/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
>
> To reproduce:
>
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="gomp.exp=gfortran.dg/gomp/target-update-1.f90 --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="gomp.exp=gfortran.dg/gomp/target-update-1.f90 --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="gomp.exp=gfortran.dg/gomp/target-update-1.f90 --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="gomp.exp=gfortran.dg/gomp/target-update-1.f90 --target_board='unix{-m64\ -march=cascadelake}'"
>
> (Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com)
prev parent reply other threads:[~2023-06-07 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 22:50 haochen.jiang
2023-06-07 7:13 ` Maxim Kuvyrkov [this message]
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=CAF06A8C-656E-4A1D-80BD-6F0BC0BDA4B0@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=haochen.jiang@intel.com \
--cc=haochenj@ecsmtp.sh.intel.com \
--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).