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/104440] nvptx: FAIL: gcc.c-torture/execute/pr53465.c  execution test
Date: Thu, 17 Feb 2022 07:20:15 +0000	[thread overview]
Message-ID: <bug-104440-4-0Vs8b1Pn6J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104440-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 52456
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52456&action=edit
Tentative patch, introducing -minit-regs=<0|1|2>

This patch fixes the problem, and survived a standalone build and gcc testsuite
run.

Currently testing in offloading setting.

Uses DF_MIR_IN, otherwise only used by pass_ree.

Effect of -minit-regs=1 (insert init at function entry):
...
        .reg.pred %r50;
        .reg.pred %r51;
        .reg.u32 %r52;
+               mov.u32 %r26, 0;
                mov.u64 %r33, %ar0;
                mov.u32 %r34, %ar1;
                setp.le.s32     %r35, %r34, 0;
...

Effect of -minit-regs=2 (insert init close to use):
...
                add.u64 %r32, %r33, %r37;
                mov.u32 %r31, 0;
                mov.u32 %r52, 1;
+               mov.u32 %r26, 0;
 $L4:
                mov.u32 %r30, %r26;
                ld.u32  %r26, [%r25];
...

  parent reply	other threads:[~2022-02-17  7:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  8:06 [Bug target/104440] New: " vries at gcc dot gnu.org
2022-02-08  8:07 ` [Bug target/104440] " vries at gcc dot gnu.org
2022-02-08  8:09 ` pinskia at gcc dot gnu.org
2022-02-08  8:11 ` pinskia at gcc dot gnu.org
2022-02-08  8:16 ` vries at gcc dot gnu.org
2022-02-08  8:22 ` pinskia at gcc dot gnu.org
2022-02-08  9:25 ` rguenth at gcc dot gnu.org
2022-02-08  9:26 ` rguenth at gcc dot gnu.org
2022-02-17  7:20 ` vries at gcc dot gnu.org [this message]
2022-02-17  7:37 ` vries at gcc dot gnu.org
2022-02-17  7:58 ` vries at gcc dot gnu.org
2022-02-20 22:48 ` vries at gcc dot gnu.org
2022-02-21 15:51 ` cvs-commit at gcc dot gnu.org
2022-02-21 15:52 ` 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-104440-4-0Vs8b1Pn6J@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).