public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92029] [10/11 Regression] 'libgomp.fortran/pr90779.f90' ICE for nvptx offloading
Date: Tue, 16 Jun 2020 14:46:38 +0000 [thread overview]
Message-ID: <bug-92029-4-x7lwtNn8us@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92029-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92029
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #9)
> This is fixed by Tobias' PR94848, PR95551 commit
> 1c0fdaf79e3618fd7512608a2e5c62b6b306e9e8 "openmp: ensure variables in
> offload table are streamed out (PRs 94848 + 95551)". Tobias, please verify
> this is expected, etc.
(I think I have written a comment at least twice but somehow it was never
saved.)
FIXED.
Comment 2 (plus comment 4) exactly describes what the patch for PR94848 and
PR95551 does.
prev parent reply other threads:[~2020-06-16 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92029-4@http.gcc.gnu.org/bugzilla/>
2020-03-20 8:51 ` [Bug tree-optimization/92029] [10 " rguenth at gcc dot gnu.org
2020-05-07 11:56 ` [Bug tree-optimization/92029] [10/11 " jakub at gcc dot gnu.org
2020-06-12 10:21 ` tschwinge at gcc dot gnu.org
2020-06-16 14:46 ` burnus at gcc dot gnu.org [this message]
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-92029-4-x7lwtNn8us@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).