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 <tob...@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)
