public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95654] New: nvptx offloading: FAIL: libgomp.fortran/pr66199-5.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
Date: Fri, 12 Jun 2020 11:33:32 +0000 [thread overview]
Message-ID: <bug-95654-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95654
Bug ID: 95654
Summary: nvptx offloading: FAIL: libgomp.fortran/pr66199-5.f90
-O3 -fomit-frame-pointer -funroll-loops -fpeel-loops
-ftracer -finline-functions execution test
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: openmp
Severity: normal
Priority: P3
Component: fortran
Assignee: burnus at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
The recent PR94690 commit f884bef21cccc05d748fd7869cd641cbb4f6b6bb "[Fortran]
OpenMP - permit lastprivate in distribute + SIMD fixes (PR94690)" added new
test cases, one of which FAILs for nvptx offloading in a high optimization
variant (only):
PASS: libgomp.fortran/pr66199-5.f90 -O0 (test for excess errors)
PASS: libgomp.fortran/pr66199-5.f90 -O0 execution test
PASS: libgomp.fortran/pr66199-5.f90 -O1 (test for excess errors)
PASS: libgomp.fortran/pr66199-5.f90 -O1 execution test
PASS: libgomp.fortran/pr66199-5.f90 -O2 (test for excess errors)
PASS: libgomp.fortran/pr66199-5.f90 -O2 execution test
PASS: libgomp.fortran/pr66199-5.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess
errors)
FAIL: libgomp.fortran/pr66199-5.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
PASS: libgomp.fortran/pr66199-5.f90 -O3 -g (test for excess errors)
PASS: libgomp.fortran/pr66199-5.f90 -O3 -g execution test
PASS: libgomp.fortran/pr66199-5.f90 -Os (test for excess errors)
PASS: libgomp.fortran/pr66199-5.f90 -Os execution test
The one FAIL is:
STOP 3
FAIL: libgomp.fortran/pr66199-5.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
Compiling manually, I'm seeing:
source-gcc/libgomp/testsuite/libgomp.fortran/pr66199-5.f90: In function
‘__m_MOD_f4._omp_fn.0’:
source-gcc/libgomp/testsuite/libgomp.fortran/pr66199-5.f90:61: warning:
‘.count.16’ may be used uninitialized in this function [-Wmaybe-uninitialized]
61 | end
|
source-gcc/libgomp/testsuite/libgomp.fortran/pr66199-5.f90: In function
‘__m_MOD_f3._omp_fn.0’:
source-gcc/libgomp/testsuite/libgomp.fortran/pr66199-5.f90:48: warning:
‘.count.102’ may be used uninitialized in this function [-Wmaybe-uninitialized]
48 | end
|
I haven't assessed whether that's relevant.
I don't see the problem when running with Intel MIC (emulated) offloading (via
setting 'CUDA_VISIBLE_DEVICES=n_o-N-e'), and I have not yet tested GCN
offloading.
next reply other threads:[~2020-06-12 11:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 11:33 tschwinge at gcc dot gnu.org [this message]
2020-06-12 14:18 ` [Bug fortran/95654] " tschwinge at gcc dot gnu.org
2020-06-12 15:40 ` burnus at gcc dot gnu.org
2020-09-09 11:27 ` burnus at gcc dot gnu.org
2020-09-15 23:29 ` burnus at gcc dot gnu.org
2020-09-16 7:24 ` burnus at gcc dot gnu.org
2020-09-16 13:23 ` vries at gcc dot gnu.org
2020-09-16 13:33 ` vries at gcc dot gnu.org
2020-09-16 15:54 ` vries at gcc dot gnu.org
2020-09-16 15:57 ` vries at gcc dot gnu.org
2020-09-16 21:11 ` burnus at gcc dot gnu.org
2020-09-17 9:33 ` burnus at gcc dot gnu.org
2020-09-17 10:20 ` vries at gcc dot gnu.org
2020-09-17 13:53 ` vries at gcc dot gnu.org
2020-09-17 15:19 ` vries at gcc dot gnu.org
2020-09-22 17:16 ` cvs-commit at gcc dot gnu.org
2020-09-25 8:55 ` burnus at gcc dot gnu.org
2020-10-05 6:54 ` cvs-commit at gcc dot gnu.org
2020-10-05 7:01 ` vries at gcc dot gnu.org
2020-10-05 7:01 ` vries at gcc dot gnu.org
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=bug-95654-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).