public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104580] New: [nvptx] Use prevent_branch_around_nothing only when necessary
Date: Thu, 17 Feb 2022 08:25:16 +0000	[thread overview]
Message-ID: <bug-104580-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104580
           Summary: [nvptx] Use prevent_branch_around_nothing only when
                    necessary
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I had the following idea:

The prevent_branch_around_nothing workaround was added to force
a uniform warp after this:
...
            {
                    .reg.u32        %x;
                    mov.u32 %x, %tid.x;
                    setp.ne.u32     %r23, %x, 0;
            }
            @%r23   bra     $L2;
    $L2:
...

With TARGET_PTX_6_0, we enforce a uniform warp by using bar.warp.sync, and
consequently this workaround is not necessary anymore.
...

However, this introduces the following regression:
...
FAIL: libgomp.fortran/task-detach-8.f90 -Os execution test
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/reduction-7.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -foffload=nvptx-none  -O0
-DGOMP_NVPTX_JIT=-O0 execution test
...

Needs investigation.  Either the idea is wrong, or the tests FAIL for some
other reason.

             reply	other threads:[~2022-02-17  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  8:25 vries at gcc dot gnu.org [this message]
2022-02-17  8:25 ` [Bug target/104580] " 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-104580-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).