From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: [PATCH 3/3] Enable full libgfortran library for AMD GCN
Date: Fri, 14 Jun 2019 16:17:00 -0000 [thread overview]
Message-ID: <CAO9iq9Gs4T1va8=MAG0Lyu4-HsNMbtsZHrnEZ6YV71z-aMtEcw@mail.gmail.com> (raw)
In-Reply-To: <a7d088ad-3a0e-d18e-5577-ee7ca0803aa3@codesourcery.com>
On Fri, Jun 7, 2019 at 5:41 PM Andrew Stubbs <ams@codesourcery.com> wrote:
>
> This patch basically reverts the previous patch to put AMD GCN in
> "minimal" mode.
This is Ok, provided the maintainers for the areas touched by the
other 2 patches in this series Ok those.
Thanks for improving Fortran offloading (given the recent Frontier
supercomputer announcement, I hope we will receive more work in this
area in the future).
--
Janne Blomqvist
next prev parent reply other threads:[~2019-06-14 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 14:38 [PATCH 0/3] Enable full libgfortran " Andrew Stubbs
2019-06-07 14:39 ` [PATCH 1/3] Create GCN-specific gthreads Andrew Stubbs
2019-06-19 8:57 ` Andrew Stubbs
2019-06-19 16:04 ` Jeff Law
2019-06-19 16:56 ` Andrew Stubbs
2019-06-19 16:59 ` Jeff Law
2023-11-03 14:54 ` GCN: Address undeclared 'NULL' usage in 'libgcc/config/gcn/gthr-gcn.h:__gthread_getspecific' (was: [PATCH 1/3] Create GCN-specific gthreads) Thomas Schwinge
2019-06-07 14:40 ` [PATCH 2/3] Stub implementation of unwinding for AMD GCN Andrew Stubbs
2019-06-19 8:58 ` Andrew Stubbs
2019-06-19 16:05 ` Jeff Law
2019-06-19 16:57 ` Andrew Stubbs
2019-06-07 14:41 ` [PATCH 3/3] Enable full libgfortran library " Andrew Stubbs
2019-06-14 16:17 ` Janne Blomqvist [this message]
2019-06-19 16:05 ` Jeff Law
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='CAO9iq9Gs4T1va8=MAG0Lyu4-HsNMbtsZHrnEZ6YV71z-aMtEcw@mail.gmail.com' \
--to=blomqvist.janne@gmail.com \
--cc=ams@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).