Fwd: GCC 7.1 Release Candidate available from gcc.gnu.org

[Michael Clark]

FYI - noticed the first GCC 7.1 release candidate including riscv support.

Begin forwarded message:

From: Jakub Jelinek <ja...@redhat.com>

Subject: GCC 7.1 Release Candidate available from gcc.gnu.org

Date: 26 April 2017 at 9:43:39 AM GMT+12

To: g...@gcc.gnu.org

Reply-To: Jakub Jelinek <ja...@redhat.com>

The first release candidate for GCC 7.1 is available from

ftp://gcc.gnu.org/pub/gcc/snapshots/7.0.1-RC-20170425

and shortly its mirrors.  It has been generated from SVN revision 247264.

I have so far bootstrapped and tested the release candidate on
x86_64-linux and i686-linux.  Please test it and report any issues to
bugzilla.

If all goes well, I'd like to release 7.1 on Tuesday, May 2nd.

[Andrew Waterman]

Sweet!

> --
> You received this message because you are subscribed to the Google Groups
> "RISC-V SW Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sw-dev+un...@groups.riscv.org.
> To post to this group, send email to sw-...@groups.riscv.org.
> Visit this group at
> https://groups.google.com/a/groups.riscv.org/group/sw-dev/.
> To view this discussion on the web visit
> https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/268719AE-0E8E-4B54-85DE-3C3D881CA55D%40mac.com.

[Tommy Murphy]

Up to now I've been building the tools as follows:

git clone --recursive https://github.com/riscv/riscv-gnu-toolchain
cd riscv-gnu-toolchain
./configure --prefix=... --enable-multilib
make

If I want to use the 7.1 RC how do the build instructions change?

Thanks.

[Kito Cheng]

​Use gcc-7.1 branch in riscv-gnu-toolchain:

​

​git clone --recursive https://github.com/riscv/riscv-gnu-toolchain​ -b ​gcc-7.1

--

You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+unsubscribe@groups.riscv.org.

To post to this group, send email to sw-...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.

To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/fbdc4bbb-7f44-47f9-a7b8-ab925b0baa73%40groups.riscv.org.

[Tommy Murphy]

Thanks a lot.
I'll try that.

[Tommy Murphy]

I actually meant to post in this thread about the actual 7.1 release (not RC).

https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/ZU5JDJzQdPU

Do the same instructions still apply if I want to build the RISC-V tools for the 7.1 release version?

Namely:

​git clone --recursive https://github.com/riscv/riscv-gnu-toolchain​ -b ​gcc-7.1

Thanks.

[Palmer Dabbelt]

I just merged the pull request, so you can use master now. In general it's
best to just always use riscv-gnu-toolchain's master branch (unless you're
getting a commit from riscv-tools or rocket-chip, in which case you should use
those). We're tracking release branches of the projects that have been
released with RISC-V support, but sometimes there's a few new patches that
we've backported that aren't in the tarballs.

Additionally we try to ensure that everything that gets merged to master builds
on Travis and passes the GCC test suite.

[Tommy Murphy]

Thanks Palmer.
So just to be clear this will get the GCC 7.1 release tools now?

[Palmer Dabbelt]

As of this commit

https://github.com/riscv/riscv-gnu-toolchain/commit/f8d9835248c63ab65797ca25fa2af8aecbce226d

which was merged 3 hours ago, that will build the GCC 7.1 release.

[Tommy Murphy]

Great - thanks a lot.