From: Joseph Myers <joseph@codesourcery.com>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 06/10] GCN back-end config
Date: Fri, 16 Nov 2018 17:44:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1811161743290.12454@digraph.polyomino.org.uk> (raw)
In-Reply-To: <30e5af6bb22bdb4ac2bd7617e8d91b72ad765e98.1542381960.git.ams@codesourcery.com>
On Fri, 16 Nov 2018, Andrew Stubbs wrote:
> * config.sub: Recognize amdgcn*-*-amdhsa.
config.sub should be copied from upstream config.git (along with
config.guess at the same time), once the support has been added there; it
shouldn't be patched locally in GCC.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-11-16 17:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 16:27 [PATCH 00/10] AMD GCN Port v2 Andrew Stubbs
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 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:28 ` [PATCH 08/10] Testsuite: GCN is always PIE Andrew Stubbs
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 03/10] GCN libgcc Andrew Stubbs
2018-11-21 0:49 ` Jeff Law
2018-11-16 16:28 ` [PATCH 02/10] GCN libgfortran Andrew Stubbs
2018-11-16 16:28 ` [PATCH 04/10] GCN machine description Andrew Stubbs
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
2018-11-16 16:29 ` [PATCH 06/10] GCN back-end config Andrew Stubbs
2018-11-16 17:44 ` Joseph Myers [this message]
2018-11-20 11:44 ` Andrew Stubbs
2018-11-21 2:32 ` 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=alpine.DEB.2.21.1811161743290.12454@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=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).