From: Richard Biener <richard.guenther@gmail.com>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3 00/10] AMD GCN Port v3
Date: Thu, 17 Jan 2019 12:55:00 -0000 [thread overview]
Message-ID: <CAFiYyc128DFes-U=3wADyQ=sYLYcb7Y5J8eE6kscQ41e3CKvTA@mail.gmail.com> (raw)
In-Reply-To: <1fb30333-cd0b-49a6-283e-29fcec5a06f8@codesourcery.com>
On Thu, Jan 17, 2019 at 1:51 PM Andrew Stubbs <ams@codesourcery.com> wrote:
>
> On 14/01/2019 13:55, Andrew Stubbs wrote:
> > I will now rebase, retest, change all the dates to 2019, and get it
> > committed.
>
> This is now done! :-)
>
> THe Newlib port is also committed, so all the pieces needed for testing
> GCN should be available to everybody now.
>
> To be clear, the libgomp port needed to support OpenMP still needs to be
> cleaned up and submitted, and the middle-end patches required to support
> OpenACC are likewise to-do (and currently depend on the openacc
> development branches, in any case).
>
> Many thanks to Jeff, both Richards, Mike, and others for reviewing the
> patches.
Please make notes in gcc-9/changes.html and update the ports matrix
in (... go find it!) and also add a news entry to index.html.
Richard.
> Andrew
prev parent reply other threads:[~2019-01-17 12:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:52 Andrew Stubbs
2018-12-12 11:52 ` [PATCH v3 02/10] GCN libgfortran Andrew Stubbs
2018-12-12 11:52 ` [PATCH 01/10] Fix LRA bug Andrew Stubbs
2018-12-13 23:49 ` Jeff Law
2018-12-14 10:04 ` Andrew Stubbs
2018-12-14 11:52 ` Andrew Stubbs
2018-12-12 11:52 ` [PATCH v3 03/10] GCN libgcc Andrew Stubbs
2018-12-12 11:53 ` [PATCH v3 07/10] Add dg-require-effective-target exceptions Andrew Stubbs
2018-12-12 11:53 ` [PATCH v3 10/10] Port testsuite to GCN Andrew Stubbs
2018-12-17 12:17 ` Andrew Stubbs
2018-12-12 11:53 ` [PATCH v3 05/10] GCN back-end code Andrew Stubbs
2024-01-31 17:12 ` GCN: Remove 'SGPR_OR_VGPR_REGNO_P' definition (was: [PATCH v3 05/10] GCN back-end code) Thomas Schwinge
2024-01-31 17:22 ` GCN: Remove 'SGPR_OR_VGPR_REGNO_P' definition Andrew Stubbs
2024-02-01 13:49 ` GCN: Don't hard-code number of SGPR/VGPR/AVGPR registers (was: [PATCH v3 05/10] GCN back-end code) Thomas Schwinge
2024-02-01 14:45 ` GCN: Don't hard-code number of SGPR/VGPR/AVGPR registers Andrew Stubbs
2018-12-12 11:53 ` [PATCH v3 04/10] GCN machine description Andrew Stubbs
2020-04-29 8:30 ` Thomas Schwinge
2024-01-31 17:21 ` GCN: Remove 'FIRST_{SGPR,VGPR,AVGPR}_REG', 'LAST_{SGPR,VGPR,AVGPR}_REG' from machine description (was: [PATCH v3 04/10] GCN machine description) Thomas Schwinge
2024-01-31 17:41 ` GCN: Remove 'FIRST_{SGPR,VGPR,AVGPR}_REG', 'LAST_{SGPR,VGPR,AVGPR}_REG' from machine description Andrew Stubbs
2018-12-12 11:53 ` [PATCH v3 09/10] Ignore LLVM's blank lines Andrew Stubbs
2018-12-12 12:07 ` Rainer Orth
2018-12-17 12:09 ` Andrew Stubbs
2018-12-13 1:32 ` Segher Boessenkool
2019-01-28 21:35 ` H.J. Lu
2018-12-12 11:53 ` [PATCH v3 06/10] GCN back-end config Andrew Stubbs
2020-03-09 15:24 ` [Patch] ./configure.ac – build libgomp by default for amdgcn*-*-* Tobias Burnus
2020-03-09 15:56 ` Jakub Jelinek
2020-04-29 8:23 ` [gcn] Don't default to building target-libstdc++-v3 [PR92713] (was: [PATCH v3 06/10] GCN back-end config) Thomas Schwinge
2018-12-12 11:53 ` [PATCH v3 08/10] Testsuite: GCN is always PIE Andrew Stubbs
2019-01-07 10:48 ` [PATCH v3 00/10] AMD GCN Port v3 Andrew Stubbs
2019-01-07 11:59 ` Richard Biener
2019-01-11 23:20 ` Jeff Law
2019-01-14 13:55 ` Andrew Stubbs
2019-01-17 12:51 ` Andrew Stubbs
2019-01-17 12:55 ` Richard Biener [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='CAFiYyc128DFes-U=3wADyQ=sYLYcb7Y5J8eE6kscQ41e3CKvTA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=ams@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
/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).