On 10/31/14 17:50, Bernd Schmidt wrote:
On 10/31/2014 09:56 PM, Jeff Law wrote:
Pondering this a bit more, I think this is fine in concept. As you
note, removing the GNU extensions or at least making them conditional
would be good since these are going to be built with the host tools.
I'm not
On 10/20/14 08:48, Bernd Schmidt wrote:
This is a bonus optional patch which adds ar, ranlib, as and ld to the
ptx port. This is not proper binutils; ar and ranlib are just linked to
the host versions, and the other two tools have the following functions:
* nvptx-as is required to convert the
On 10/31/2014 09:56 PM, Jeff Law wrote:
Pondering this a bit more, I think this is fine in concept. As you
note, removing the GNU extensions or at least making them conditional
would be good since these are going to be built with the host tools.
I'm not going to dig into the implementations...
On 10/22/14 15:11, Bernd Schmidt wrote:
On 10/22/2014 10:31 PM, Jeff Law wrote:
These tools currently require GNU extensions - something I probably
ought to fix if we decide to add them to the gcc build itself.
Would these be more appropriate in binutils?
I don't think so, given that we
On 10/20/14 08:48, Bernd Schmidt wrote:
This is a bonus optional patch which adds ar, ranlib, as and ld to the
ptx port. This is not proper binutils; ar and ranlib are just linked to
the host versions, and the other two tools have the following functions:
* nvptx-as is required to convert the
On 10/22/2014 10:31 PM, Jeff Law wrote:
These tools currently require GNU extensions - something I probably
ought to fix if we decide to add them to the gcc build itself.
Would these be more appropriate in binutils?
I don't think so, given that we don't need any piece of regular
binutils.
On Mon, 20 Oct 2014, Bernd Schmidt wrote:
These tools currently require GNU extensions - something I probably ought to
fix if we decide to add them to the gcc build itself.
And as regards library use, I'd expect the sources to start with #includes
of config.h and system.h (and so not include
