Update nvptx newlib installation requirements

Message ID 3632bf91-4d62-a402-c430-aad363fe294e@codesourcery.com
State New
Headers show
Series
  • Update nvptx newlib installation requirements
Related show

Commit Message

Cesar Philippidis April 23, 2018, 2:22 p.m.
The nvptx port has been merged into newlib, so the Mentor Embedded
github repository is no longer needed. While we're still maintaining the
github mirror, given the stability of the nvptx port, going forward I
expect all of the development to occur in the upstream newlib repository
directly.

This patch updates the install documentation to point the the upstream
newlib sources instead of the Mentor Embedded github mirror. I don't see
tarballs for any point releases on newlib's website, so I added a
reference to the git revision containing nvptx port.

Is this OK for trunk?

Thanks,
Cesar

Comments

Richard Biener April 24, 2018, 7:10 a.m. | #1
On Mon, Apr 23, 2018 at 4:22 PM, Cesar Philippidis
<cesar@codesourcery.com> wrote:
> The nvptx port has been merged into newlib, so the Mentor Embedded

> github repository is no longer needed. While we're still maintaining the

> github mirror, given the stability of the nvptx port, going forward I

> expect all of the development to occur in the upstream newlib repository

> directly.

>

> This patch updates the install documentation to point the the upstream

> newlib sources instead of the Mentor Embedded github mirror. I don't see

> tarballs for any point releases on newlib's website, so I added a

> reference to the git revision containing nvptx port.

>

> Is this OK for trunk?


That's great news!  Note that we usually keep copies of build dependences at
ftp://gcc.gnu.org/pub/gcc/infrastructure/ and there's currently no nvptx newlib
variant there.  Maybe you can prepare a tarball that's ready to plug into gcc
sources with the nvptx support included?

Otherwise OK.

Btw, can you also update the GCC wiki with regarding to this change?

Thanks,
Richard.

> Thanks,

> Cesar
Cesar Philippidis April 24, 2018, 4 p.m. | #2
On 04/24/2018 12:10 AM, Richard Biener wrote:

> That's great news!  Note that we usually keep copies of build dependences at

> ftp://gcc.gnu.org/pub/gcc/infrastructure/ and there's currently no nvptx newlib

> variant there.  Maybe you can prepare a tarball that's ready to plug into gcc

> sources with the nvptx support included?


How do I go about uploading tarball to that ftp server?

I could be mistaken, but I think that GCC's build system would need to
be taught how to build nvptx-tools automatically like newlib. And that's
likely a stage 1 task. But in the meantime, having tarballs for the
build dependencies would be nice.

> Otherwise OK.

> 

> Btw, can you also update the GCC wiki with regarding to this change?


Done. I added a new 'Build Dependencies' section to the nvptx wiki:

https://gcc.gnu.org/wiki/nvptx

Cesar
Richard Biener April 25, 2018, 7:51 a.m. | #3
On Tue, Apr 24, 2018 at 6:00 PM, Cesar Philippidis
<cesar@codesourcery.com> wrote:
> On 04/24/2018 12:10 AM, Richard Biener wrote:

>

>> That's great news!  Note that we usually keep copies of build dependences at

>> ftp://gcc.gnu.org/pub/gcc/infrastructure/ and there's currently no nvptx newlib

>> variant there.  Maybe you can prepare a tarball that's ready to plug into gcc

>> sources with the nvptx support included?

>

> How do I go about uploading tarball to that ftp server?


Anybody with privileges (like me...) can put it there.

> I could be mistaken, but I think that GCC's build system would need to

> be taught how to build nvptx-tools automatically like newlib. And that's

> likely a stage 1 task. But in the meantime, having tarballs for the

> build dependencies would be nice.


Yes.  Note that dependences that need to be installed are fine as well,
it is after all the usual mode of operation.

>> Otherwise OK.

>>

>> Btw, can you also update the GCC wiki with regarding to this change?

>

> Done. I added a new 'Build Dependencies' section to the nvptx wiki:

>

> https://gcc.gnu.org/wiki/nvptx

>

> Cesar

Patch

[nvptx] Update newlib dependency.

2018-04-23  Cesar Philippidis  <cesar@codesourcery.com>

	gcc/
	* doc/install.texi: Update newlib dependency for nvptx.

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 64ad2445a33..121a821857f 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -4205,11 +4205,11 @@  Instead of GNU binutils, you will need to install
 Tell GCC where to find it:
 @option{--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin}.
 
-A nvptx port of newlib is available at
-@uref{https://github.com/MentorEmbedded/nvptx-newlib/,,nvptx-newlib}.
-It can be automatically built together with GCC@.  For this, add a
-symbolic link to nvptx-newlib's @file{newlib} directory to the
-directory containing the GCC sources.
+You will need newlib 3.0 git revision
+cd31fbb2aea25f94d7ecedc9db16dfc87ab0c316 or later.  It can be
+automatically built together with GCC@.  For this, add a symbolic link
+to nvptx-newlib's @file{newlib} directory to the directory containing
+the GCC sources.
 
 Use the @option{--disable-sjlj-exceptions} and
 @option{--enable-newlib-io-long-long} options when configuring.