Re: Bootstrap failure on aarch64-linux-gnu with trunk

2017-01-13 Thread Gerald Pfeifer
On Fri, 13 Jan 2017, Jeff Law wrote: > I'm pretty sure its my DSE changes. I'm seeing similar failures on > ppc64le and am about to revert once a bit more testing is complete. I've been seeing this on i386-unknown-freebsd as well. Gerald

Re: Bootstrap failure on aarch64-linux-gnu with trunk

2017-01-13 Thread Jeff Law
On 01/13/2017 05:57 PM, Andrew Pinski wrote: On Fri, Jan 13, 2017 at 3:56 PM, Jeff Law wrote: On 01/13/2017 04:54 PM, Andrew Pinski wrote: Between revision 244386 and 28, aarch64-linux-gnu started to miscompare bootstrap. These are the options I used: --prefix=`pwd`/../tools \ --enable-l

Re: Bootstrap failure on aarch64-linux-gnu with trunk

2017-01-13 Thread Jeff Law
On 01/13/2017 07:35 PM, David Edelsohn wrote: On Fri, Jan 13, 2017 at 6:56 PM, Jeff Law wrote: On 01/13/2017 04:54 PM, Andrew Pinski wrote: Between revision 244386 and 28, aarch64-linux-gnu started to miscompare bootstrap. These are the options I used: --prefix=`pwd`/../tools \ --enable-

Re: Bootstrap failure on aarch64-linux-gnu with trunk

2017-01-13 Thread David Edelsohn
On Fri, Jan 13, 2017 at 6:56 PM, Jeff Law wrote: > On 01/13/2017 04:54 PM, Andrew Pinski wrote: >> >> Between revision 244386 and 28, aarch64-linux-gnu started to >> miscompare bootstrap. >> >> These are the options I used: >> --prefix=`pwd`/../tools \ >> --enable-languages=c,c++,fortran,go \

Re: Help with integrating my test program into dejagnu

2017-01-13 Thread Daniel Santos
Sorry for my delayed response. I've been a bit under the weather lately. On 01/11/2017 10:46 AM, Mike Stump wrote: After running using DG_TORTURE_OPTIONS, But why? I think you missed what you're testing. You aren't creating or looking for bugs in the optimizer. Your test case isn't for an

Re: Successful bootstrap and install of gcc (GCC) 6.3.0 on mips64el-unknown-linux-gnu

2017-01-13 Thread Aaro Koskinen
Hi, On Mon, Jan 09, 2017 at 10:20:12AM +0100, Dennis Luehring wrote: > are you only building gcc or also glibc/binutils? and building a kernel with > minimal hello world init or something for testing? I always also rebuild the full rootfs and kernel, and run those in my machines. > what about a

Re: Bootstrap failure on aarch64-linux-gnu with trunk

2017-01-13 Thread Andrew Pinski
On Fri, Jan 13, 2017 at 3:56 PM, Jeff Law wrote: > On 01/13/2017 04:54 PM, Andrew Pinski wrote: >> >> Between revision 244386 and 28, aarch64-linux-gnu started to >> miscompare bootstrap. >> >> These are the options I used: >> --prefix=`pwd`/../tools \ >> --enable-languages=c,c++,fortran,go \

Re: Bootstrap failure on aarch64-linux-gnu with trunk

2017-01-13 Thread Jeff Law
On 01/13/2017 04:54 PM, Andrew Pinski wrote: Between revision 244386 and 28, aarch64-linux-gnu started to miscompare bootstrap. These are the options I used: --prefix=`pwd`/../tools \ --enable-languages=c,c++,fortran,go \ --with-cpu=thunderx \ --disable-werr

Bootstrap failure on aarch64-linux-gnu with trunk

2017-01-13 Thread Andrew Pinski
Between revision 244386 and 28, aarch64-linux-gnu started to miscompare bootstrap. These are the options I used: --prefix=`pwd`/../tools \ --enable-languages=c,c++,fortran,go \ --with-cpu=thunderx \ --disable-werror --with-sysroot=/ --enable-plugins \

A

2017-01-13 Thread georg storaker
Sent from my iPhone

Re: Help with integrating my test program into dejagnu

2017-01-13 Thread Mike Stump
On Jan 11, 2017, at 3:29 PM, Daniel Santos wrote: > On 01/11/2017 12:25 PM, Joseph Myers wrote: > Would this then be the correct test? Yeah, looks good.

Multilib seems to fail for mingw-w64 build

2017-01-13 Thread FX
Hi, I am trying to compile a multilib-enabled GCC cross-compiler targetting mingw-w64. I have the mingw-w64 headers installed, the CRT built for both 32- and 64-bit, and installed (with libs in $ROOT/x86_64-w64-mingw32/lib32 and $ROOT/x86_64-w64-mingw32/lib respectively). Building the compiler