This is the mail archive of the
mailing list for the GCC project.
Re: The nvptx port [10/11+] Target files
- From: Bernd Schmidt <bernds at codesourcery dot com>
- To: Jeff Law <law at redhat dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 30 Oct 2014 00:55:04 +0100
- Subject: Re: The nvptx port [10/11+] Target files
- Authentication-results: sourceware.org; auth=none
- References: <54451994 dot 9070209 at codesourcery dot com> <54451D57 dot 5050803 at codesourcery dot com> <5447F0E1 dot 7080906 at redhat dot com> <544FAE8B dot 5010906 at codesourcery dot com> <545179C6 dot 4030406 at redhat dot com>
On 10/30/2014 12:35 AM, Jeff Law wrote:
A "nit" -- Richard S. recently removed the need to include the "enum"
for "enum machine_mode". I believe he had a script to handle the
mundane parts of that change. Please make sure to update the nvptx port
to conform to that new convention, obviously feel free to use the script
if you want.
You may need to update with James Greenhalgh's changes to
MOVE_BY_PIECES_P and friends.
Ok, I'll look into those.
With those two issues addressed as needed, this is OK for the trunk.
Thanks! I've pinged some of the preliminary patches that went unapproved
up to this point.
One leftover issue, discussed in the [0/11] mail - what amount of
documentation is appropriate for this, given that we don't want to
support using this as anything other than an offload compiler? Should I
still add all the standard invoke.texi/gccint.texi pieces?
I notice that you've got some OpenMP bits (write_as_kernel). Are y'all
doing any testing with OpenMP or is that an artifact of layering OpenACC
on top of the OpenMP infrastructure?
The distinction between .kernel and .func is really not to do with
either - only .kernels are callable from the host, and only .funcs are
callable from within ptx code.