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 target/95864] New: [11 Regression] GCN offloading execution regressions after commit f062c3f11505b70c5275e5bc0e52f3e441f8afbc "amdgcn: Switch to HSACO v3 binary format"
Date: Wed, 24 Jun 2020 11:39:58 +0000 [thread overview]
Message-ID: <bug-95864-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95864
Bug ID: 95864
Summary: [11 Regression] GCN offloading execution regressions
after commit f062c3f11505b70c5275e5bc0e52f3e441f8afbc
"amdgcn: Switch to HSACO v3 binary format"
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: openmp
Severity: normal
Priority: P3
Component: target
Assignee: ams at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jules at gcc dot gnu.org
Target Milestone: ---
Target: gcn
I'm seeing the following GCN offloading execution regressions after commit
f062c3f11505b70c5275e5bc0e52f3e441f8afbc "amdgcn: Switch to HSACO v3 binary
format":
PASS: libgomp.c/../libgomp.c-c++-common/for-5.c (test for excess errors)
[-PASS:-]{+WARNING: program timed out.+}
{+FAIL:+} libgomp.c/../libgomp.c-c++-common/for-5.c execution test
libgomp: GCN fatal error: Asynchronous queue error
Runtime message: HSA_STATUS_ERROR_INVALID_ISA: The instruction set
architecture is invalid.
WARNING: program timed out.
FAIL: libgomp.c/../libgomp.c-c++-common/for-5.c execution test
Same for C++.
PASS: libgomp.c/../libgomp.c-c++-common/for-6.c (test for excess errors)
[-PASS:-]{+WARNING: program timed out.+}
{+FAIL:+} libgomp.c/../libgomp.c-c++-common/for-6.c execution test
Same as above, same for C++.
@@ -3456,9 +3460,11 @@ PASS: libgomp.fortran/optional-map.f90 -O1
execution test
PASS: libgomp.fortran/optional-map.f90 -O2 (test for excess errors)
PASS: libgomp.fortran/optional-map.f90 -O2 execution test
PASS: libgomp.fortran/optional-map.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess
errors)
[-PASS:-]{+WARNING: program timed out.+}
{+FAIL:+} libgomp.fortran/optional-map.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
PASS: libgomp.fortran/optional-map.f90 -O3 -g (test for excess errors)
[-PASS:-]{+WARNING: program timed out.+}
{+FAIL:+} libgomp.fortran/optional-map.f90 -O3 -g execution test
PASS: libgomp.fortran/optional-map.f90 -Os (test for excess errors)
PASS: libgomp.fortran/optional-map.f90 -Os execution test
Same as above.
@@ -4323,9 +4329,11 @@ PASS: libgomp.fortran/target1.f90 -O1 execution
test
PASS: libgomp.fortran/target1.f90 -O2 (test for excess errors)
PASS: libgomp.fortran/target1.f90 -O2 execution test
PASS: libgomp.fortran/target1.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
[-PASS:-]{+WARNING: program timed out.+}
{+FAIL:+} libgomp.fortran/target1.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
PASS: libgomp.fortran/target1.f90 -O3 -g (test for excess errors)
[-PASS:-]{+WARNING: program timed out.+}
{+FAIL:+} libgomp.fortran/target1.f90 -O3 -g execution test
PASS: libgomp.fortran/target1.f90 -Os (test for excess errors)
PASS: libgomp.fortran/target1.f90 -Os execution test
Same as above.
That's testing the default multilib on "Advanced Micro Devices, Inc. [AMD/ATI]
Fiji [Radeon R9 FURY / NANO Series] (rev ca)" hardware. (I haven't tested
anything else.)
There seems to be some bug?
But also:
The error reporting seems "strange"?
We shouldn't run into a timeout? (Missing unlocking on error path?)
next reply other threads:[~2020-06-24 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 11:39 tschwinge at gcc dot gnu.org [this message]
2020-06-24 13:16 ` [Bug target/95864] " ams at gcc dot gnu.org
2020-06-24 14:05 ` rguenth at gcc dot gnu.org
2020-10-06 10:23 ` tschwinge 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-95864-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).