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/107344] GCC/nvptx SESE region optimization
Date: Fri, 21 Oct 2022 09:34:05 +0000 [thread overview]
Message-ID: <bug-107344-4-kmsIGDD77N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107344-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107344
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2022-10-21
Status|UNCONFIRMED |NEW
--- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Regression 'libgomp.oacc-c-c++-common/nvptx-sese-1.c' addressed, but this
remains to be looked into:
(In reply to Thomas Schwinge from comment #0)
> GCC/nvptx has a "SESE region optimization", <https://inbox.sourceware.org/gcc-patches/564CC75D.3020309@acm.org>.
>
> [...]
>
> During investigation of that issue (which I suppose is just one random example), I found that earlier code transformations/optimizations may inhibit this "Neuter whole SESE regions" optimization.
>
> It's unclear to me if this is an actual "problem", which optimization is "more important".
next prev parent reply other threads:[~2022-10-21 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 9:24 [Bug target/107344] New: " tschwinge at gcc dot gnu.org
2022-10-21 9:29 ` [Bug target/107344] " cvs-commit at gcc dot gnu.org
2022-10-21 9:34 ` tschwinge at gcc dot gnu.org [this message]
2022-10-21 11:17 ` rguenth 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-107344-4-kmsIGDD77N@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).