public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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: Tue, 08 Feb 2022 09:26:43 +0000 [thread overview]
Message-ID: <bug-104440-4-S7sQWgZ5W1@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 #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #6)
> (In reply to Andrew Pinski from comment #5)
> > (In reply to Tom de Vries from comment #4)
> > > (In reply to Andrew Pinski from comment #2)
> > > > I thought there was another bug that reported a similar issue.
> > >
> > > You mean related to nvptx, or in general?
> >
> > It was in general. PR 21111 is related but not the same issue.
> >
> >
> > PR 61810 is the one pointing out the problems with init-regs and talking
> > about removing it.
>
> I think there's a bug that ifcombine produces the situation and that
> valgrind complains about uninitialized uses.
>
> Note that indeed the init-regs pass should go away.
>
> It's somewhat unfeasible to compute a must-initialized regs so the issue
> is really hard to avoid. But nobody tried yet (it would also come at a cost
> of course). It would definitely inhibit all early short-circuiting on
> GENERIC (a good thing, but with a lot of fallout I think).
>
> That said, --param logical-op-non-short-circuit=0 is only a workaround until
> you hit ifcombine doing similar transforms.
>
> LOGICAL_OP_NON_SHORT_CIRCUIT is a target macro btw, so you could arrange it
> to be zero for nvptx (but that's of course too late since the hosts
> LOGICAL_OP_NON_SHORT_CIRCUIT value will be used).
But it would at least prevent ifcombine from doing the transform (ifcombine
only runs on the offload side).
next prev parent reply other threads:[~2022-02-08 9:26 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 [this message]
2022-02-17 7:20 ` vries at gcc dot gnu.org
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-S7sQWgZ5W1@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).