This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/79236] New: [7 Regression] Many libgomp tests fail if configured with --enable-offload-targets=nvptx-none but NVidia HW or libcuda.so.1 unavailable
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 25 Jan 2017 22:21:43 +0000
- Subject: [Bug middle-end/79236] New: [7 Regression] Many libgomp tests fail if configured with --enable-offload-targets=nvptx-none but NVidia HW or libcuda.so.1 unavailable
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79236
Bug ID: 79236
Summary: [7 Regression] Many libgomp tests fail if configured
with --enable-offload-targets=nvptx-none but NVidia HW
or libcuda.so.1 unavailable
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
Many tests with combined simd constructs in target regions fail (timeout,
crash, ...) if nvptx-none offloading is configured, but fallback needs to be
used for whatever reason.
E.g.
FAIL: libgomp.c++/for-13.C execution test
FAIL: libgomp.c++/for-14.C execution test
FAIL: libgomp.c++/pr66199-5.C execution test
FAIL: libgomp.c++/pr66199-7.C execution test
FAIL: libgomp.c++/pr66199-8.C execution test
FAIL: libgomp.c/examples-4/teams-5.c execution test
FAIL: libgomp.c/examples-4/teams-6.c execution test
FAIL: libgomp.c/for-5.c execution test
FAIL: libgomp.c/for-6.c execution test
FAIL: libgomp.c/pr66199-5.c execution test
FAIL: libgomp.c/pr66199-7.c execution test
FAIL: libgomp.c/pr66199-8.c execution test
FAIL: libgomp.fortran/examples-4/teams-5.f90 -O1 execution test
FAIL: libgomp.fortran/examples-4/teams-5.f90 -O2 execution test
FAIL: libgomp.fortran/examples-4/teams-5.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
FAIL: libgomp.fortran/examples-4/teams-5.f90 -O3 -g execution test
FAIL: libgomp.fortran/examples-4/teams-5.f90 -Os execution test
FAIL: libgomp.fortran/examples-4/teams-6.f90 -O1 execution test
FAIL: libgomp.fortran/examples-4/teams-6.f90 -O2 execution test
FAIL: libgomp.fortran/examples-4/teams-6.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
FAIL: libgomp.fortran/examples-4/teams-6.f90 -O3 -g execution test
FAIL: libgomp.fortran/examples-4/teams-6.f90 -Os execution test
FAIL: libgomp.fortran/nestedfn5.f90 -O1 execution test
FAIL: libgomp.fortran/nestedfn5.f90 -O2 execution test
FAIL: libgomp.fortran/nestedfn5.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: libgomp.fortran/nestedfn5.f90 -O3 -g execution test
FAIL: libgomp.fortran/nestedfn5.f90 -Os execution test
FAIL: libgomp.fortran/target1.f90 -O1 execution test
FAIL: libgomp.fortran/target1.f90 -O2 execution test
FAIL: libgomp.fortran/target1.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: libgomp.fortran/target1.f90 -O3 -g execution test
FAIL: libgomp.fortran/target1.f90 -Os execution test
FAIL: libgomp.fortran/target6.f90 -O1 execution test
FAIL: libgomp.fortran/target6.f90 -O2 execution test
FAIL: libgomp.fortran/target6.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: libgomp.fortran/target6.f90 -O3 -g execution test
FAIL: libgomp.fortran/target6.f90 -Os execution test
all fail in that case.