gcc-8-20180408 is now available

2018-04-08 Thread gccadmin
Snapshot gcc-8-20180408 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/8-20180408/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision

Re: Patching the GCC build system to build MPICH and OpenCoarrays

2018-04-08 Thread Damian Rouson
On April 4, 2018 at 1:12:25 AM, Richard Biener (richard.guent...@gmail.com(mailto:richard.guent...@gmail.com)) wrote:   > In that case user programs compiled with -fcoarray=lib are but gfortran > or libgfortran itself is not linked against OpenCoarrays? Yes.  OpenCoarrays produces the parallel ru

Re: GCC changes for Fedora + riscv64

2018-04-08 Thread Richard W.M. Jones
On Sun, Apr 08, 2018 at 09:22:07AM -0600, Jeff Law wrote: > On 03/31/2018 12:27 PM, Richard W.M. Jones wrote: > > Hi GCC maintainers! > > > > I'd like to talk about what changes we (may) need to GCC in > > Fedora to get it working on 64-bit RISC-V, and also (more > > importantly) to ask your advic

Re: GCC changes for Fedora + riscv64

2018-04-08 Thread Jeff Law
On 03/31/2018 12:27 PM, Richard W.M. Jones wrote: > Hi GCC maintainers! > > I'd like to talk about what changes we (may) need to GCC in > Fedora to get it working on 64-bit RISC-V, and also (more > importantly) to ask your advice on things we don't fully > understand yet. However, I don't know ev

Re: Internal compiler error building libstdc++ for vax

2018-04-08 Thread Jeff Law
On 04/02/2018 10:15 AM, co...@sdf.org wrote: > It turns out (all from krister, I am still totally lost) that it is not > failing for this specific reason in this case. > > Rather, the attached patch from krister fixes it, saying that gcc > wants to change the label and then doesn't recognise the n