[Bug target/100657] New: [GCN offloading] 'libgomp.c-c++-common/reduction-6.c' execution times out

[Bug target/100657] New: [GCN offloading] 'libgomp.c-c++-common/reduction-6.c' execution times out

[tschwinge at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100657

            Bug ID: 100657
           Summary: [GCN offloading] 'libgomp.c-c++-common/reduction-6.c'
                    execution times out
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: openmp
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tschwinge at gcc dot gnu.org
                CC: ams at gcc dot gnu.org, burnus at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, jules at gcc dot gnu.org
  Target Milestone: ---
            Target: gcn

For GCN '-foffload=amdgcn-amdhsa=-march=gfx908' (only), the
'libgomp.c-c++-common/reduction-6.c' testcase recently added with commit
r12-614-g33b647956caa977d1ae489f9baed9cef70b4f382 "OpenMP: Fix SIMT for
complex/float reduction with && and ||" seems to consistently time out, both C
and C++ execution testing.  On other GCN/other offloading configurations it
seems almost instantaneous to execute.  I've confirmed this on both our
amd-instinct1 and amd-instinct2 systems.

[Bug target/100657] [GCN offloading] 'libgomp.c-c++-common/reduction-6.c' execution times out

[tschwinge at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100657

Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Same timeouts then also seen for 'libgomp.c-c++-common/reduction-5.c', again
only for gfx908.

But now, I'm happy to report that these issues disappeared after we got the
gfx908 GPU cards replaced, after they'd generally gotten very unreliable.