public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [PATCH 00/10] AMD GCN Port v2
Date: Fri, 16 Nov 2018 16:27:00 -0000	[thread overview]
Message-ID: <cover.1542381960.git.ams@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

This is a reworked version of the remaining parts of the patch series I
posted on September 5th.  As before, the series contains the
non-OpenACC/OpenMP portions of a port to AMD GCN3 and GCN5 GPU
processors.  It's sufficient to build single-threaded programs, with
vectorization in the usual way.  C and Fortran are supported, C++ is not
supported, and the other front-ends have not been tested.  The
OpenACC/OpenMP/libgomp portion will follow, once this is committed,
eventually.

Of the original 25 patches, 11 have been committed and 3 have been
dropped (no longer necessary or fixed another way).

There were also 3 patches that needed more work, but don't prevent the
toolchain from building so I've postponed them to be revisited later
(name mangling, vector size switching, elementwise loading).  There will
be some additional test failures until these issues are fixed.

Of the remaining 8 patches, 3 are already approved and are included here
for completeness only.

I've split the back-end patch into three parts to avoid the mailing list
size limit, so now there are 10 patches in this series.

Patch 01/10 is now the only target independent patch remaining.  Without
this the toolchain will not build libgfortran successfully.

The rest are all the various parts of the GCN back-end.

I still haven't got around to writing the documentation, but that can
still be done in time for the release.

-- 
Andrew
Mentor Graphics / CodeSourcery

             reply	other threads:[~2018-11-16 16:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:27 Andrew Stubbs [this message]
2018-11-16 16:27 ` [PATCH 01/10] Fix IRA ICE Andrew Stubbs
2018-11-21  0:47   ` Jeff Law
2018-11-21 11:35     ` Andrew Stubbs
2018-12-08 12:15       ` Richard Sandiford
2018-12-08 16:23         ` Jeff Law
2018-12-10 15:22           ` Andrew Stubbs
2018-11-16 16:28 ` [PATCH 04/10] GCN machine description Andrew Stubbs
2018-11-16 16:28 ` [PATCH 02/10] GCN libgfortran Andrew Stubbs
2018-11-16 16:28 ` [PATCH 03/10] GCN libgcc Andrew Stubbs
2018-11-21  0:49   ` Jeff Law
2018-11-16 16:28 ` [PATCH 09/10] Ignore LLVM's blank lines Andrew Stubbs
2018-11-16 16:28 ` [PATCH 05/10] GCN back-end code Andrew Stubbs
2018-11-16 16:28 ` [PATCH 08/10] Testsuite: GCN is always PIE Andrew Stubbs
2018-11-16 16:28 ` [PATCH 07/10] Add dg-require-effective-target exceptions Andrew Stubbs
2018-11-26 22:08   ` Mike Stump
2018-11-27  9:29     ` Andrew Stubbs
2018-11-16 16:29 ` [PATCH 06/10] GCN back-end config Andrew Stubbs
2018-11-16 17:44   ` Joseph Myers
2018-11-20 11:44     ` Andrew Stubbs
2018-11-21  2:32   ` Jeff Law
2018-11-16 16:29 ` [PATCH 10/10] Port testsuite to GCN Andrew Stubbs
2018-11-21  1:01   ` Jeff Law
2018-11-26 20:04     ` Mike Stump
2018-11-26 21:13       ` Mike Stump
2018-11-27  9:27         ` Andrew Stubbs
2018-12-06 16:10         ` Andrew Stubbs
2018-12-06 15:27     ` Andrew Stubbs
2018-12-08 12:05       ` Richard Sandiford

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=cover.1542381960.git.ams@codesourcery.com \
    --to=ams@codesourcery.com \
    --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).