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 fortran/95654] nvptx offloading: FAIL: libgomp.fortran/pr66199-5.f90   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
Date: Fri, 12 Jun 2020 14:18:41 +0000	[thread overview]
Message-ID: <bug-95654-4-xDTtwNP9uO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95654-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Tobias, I see you've unassigned yourself here, and set Depends on: PR95109. 
Have you verified that it's the same underlying issue, or do you just want to
wait for PR95109 being resolved before analyzing this one here, as it might be
the same underlying issue?  And, if you're not going to work on these items
now, is there any time scale?

  reply	other threads:[~2020-06-12 14:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 11:33 [Bug fortran/95654] New: " tschwinge at gcc dot gnu.org
2020-06-12 14:18 ` tschwinge at gcc dot gnu.org [this message]
2020-06-12 15:40 ` [Bug fortran/95654] " burnus at gcc dot gnu.org
2020-09-09 11:27 ` burnus at gcc dot gnu.org
2020-09-15 23:29 ` burnus at gcc dot gnu.org
2020-09-16  7:24 ` burnus at gcc dot gnu.org
2020-09-16 13:23 ` vries at gcc dot gnu.org
2020-09-16 13:33 ` vries at gcc dot gnu.org
2020-09-16 15:54 ` vries at gcc dot gnu.org
2020-09-16 15:57 ` vries at gcc dot gnu.org
2020-09-16 21:11 ` burnus at gcc dot gnu.org
2020-09-17  9:33 ` burnus at gcc dot gnu.org
2020-09-17 10:20 ` vries at gcc dot gnu.org
2020-09-17 13:53 ` vries at gcc dot gnu.org
2020-09-17 15:19 ` vries at gcc dot gnu.org
2020-09-22 17:16 ` cvs-commit at gcc dot gnu.org
2020-09-25  8:55 ` burnus at gcc dot gnu.org
2020-10-05  6:54 ` cvs-commit at gcc dot gnu.org
2020-10-05  7:01 ` vries at gcc dot gnu.org
2020-10-05  7:01 ` 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-95654-4-xDTtwNP9uO@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).