Re: GCC 4.0.1 RC3
Mark Mitchell [EMAIL PROTECTED] wrote: GCC 4.0.1 RC3 is now available here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050702/ With luck, this will be the last 4.0.1 release candidate. Please do download tarballs from the above URL and confirm that they work OK on your systems. sh4-unknown-linux-gnu is ok: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00354.html Regards, kaz
Re: GCC 4.0.1 RC3
Kaz Kojima wrote: Mark Mitchell [EMAIL PROTECTED] wrote: GCC 4.0.1 RC3 is now available here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050702/ With luck, this will be the last 4.0.1 release candidate. Please do download tarballs from the above URL and confirm that they work OK on your systems. sh4-unknown-linux-gnu is ok: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00354.html Thanks! -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
RE: GCC 4.0.1 RC3
Original Message From: Mark Mitchell Sent: 03 July 2005 19:21 GCC 4.0.1 RC3 is now available here: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00373.html Cygwin's ok. Still some apparent g++ regressions, relative to 4.0.0, but everything's better than 4.0.1 RC1's results. [EMAIL PROTECTED] tsts]$ diff b4.txt af.txt 10a11,12 FAIL: g++.dg/template/repo1.C (test for excess errors) FAIL: g++.dg/template/repo3.C (test for excess errors) 30a33,38 FAIL: g++.old-deja/g++.pt/instantiate4.C (test for excess errors) FAIL: g++.old-deja/g++.pt/instantiate6.C (test for excess errors) FAIL: g++.old-deja/g++.pt/repo1.C (test for excess errors) FAIL: g++.old-deja/g++.pt/repo2.C (test for excess errors) FAIL: g++.old-deja/g++.pt/repo3.C (test for excess errors) FAIL: g++.old-deja/g++.pt/repo4.C (test for excess errors) No other significant changes to report. I have really no knowledge of what's going on here with templates and repositories; do you want to see the .log file? cheers, DaveK -- Can't think of a witty .sigline today
Re: GCC 4.0.1 RC3
Eric Botcazou wrote: We have 1 new failure on SPARC/Solaris 2.5.1, 2.6 and 7 over RC2: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00137.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00138.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00139.html WARNING: program timed out. FAIL: 21_strings/basic_string/cons/char/1.cc execution test try { std::string str03(csz01 - 1, 'z'); --- stuck here This didn't happen in RC2 and I've not investigated what changed. The code is the same on Solaris 7 and 8, but the Solaris 2.5.1, 2.6 and 7 machines are substantially more limited than the Solaris 8, 9 and 10 machines. Hmph. I'm not going to worry about this too much, on the grounds that Solaris 7 is pretty old now... Thanks for the report! -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
Re: GCC 4.0.1 RC3
Ulrich Weigand wrote: Mark Mitchell wrote: GCC 4.0.1 RC3 is now available here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050702/ With luck, this will be the last 4.0.1 release candidate. Please do download tarballs from the above URL and confirm that they work OK on your systems. s390(x)-ibm-linux is still looking good: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00182.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00183.html Thanks. -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
Re: GCC 4.0.1 RC3
On Sunday 03 July 2005 19:21, Mark Mitchell wrote: GCC 4.0.1 RC3 is now available here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050702/ With luck, this will be the last 4.0.1 release candidate. Please do download tarballs from the above URL and confirm that they work OK on your systems. arm-none-elf results are ok. No new regression from 4.0.0. http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00254.html Paul
Re: GCC 4.0.1 RC3
Paul Brook wrote: On Sunday 03 July 2005 19:21, Mark Mitchell wrote: GCC 4.0.1 RC3 is now available here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050702/ With luck, this will be the last 4.0.1 release candidate. Please do download tarballs from the above URL and confirm that they work OK on your systems. arm-none-elf results are ok. No new regression from 4.0.0. http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00254.html Thanks! -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
Re: GCC 4.0.1 RC3
On Mon, Jul 04, 2005 at 01:55:52PM -0400, Andrew Pinski wrote: On Jul 4, 2005, at 1:48 PM, H. J. Lu wrote: On Sun, Jul 03, 2005 at 11:21:15AM -0700, Mark Mitchell wrote: GCC 4.0.1 RC3 is now available here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050702/ With luck, this will be the last 4.0.1 release candidate. Please do download tarballs from the above URL and confirm that they work OK on your systems. Can someone verify the missing debug info bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22295 It is a regression from 3.4. Is a known issue? Yes it is PR 21828. I proposed patches for PR 21828 at http://gcc.gnu.org/ml/gcc-patches/2005-07/msg00270.html H.J.
Re: GCC 4.0.1 RC3
AIX is good: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00216.html David
Re: GCC 4.0.1 RC3
Darwin here: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00221.html ok so far. Andreas
Re: GCC 4.0.1 RC3
PA is ok: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00223.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00218.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00186.html The failure of pr21817-1.c on hppa2.0w-hp-hpux11.11 is a minor testsuite issue that is now fixed on the trunk. The failure of asm-subreg-1.c on hppa64-hp-hpux11.11 is probably a regression although there is some debate about that: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20491. The failure of ext/array_allocator/2.cc on hppa64-hp-hpux11.11 is a latent bug on 64-bit strictly aligned targets: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19495. Fixing it requires a v3 library version bump. Dave -- J. David Anglin [EMAIL PROTECTED] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
Re: GCC 4.0.1 RC3
GCC 4.0.1 RC3 is now available here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050702/ With luck, this will be the last 4.0.1 release candidate. SPARC/Solaris 8, 9, 10 are OK: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00140.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00141.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00142.html We have 1 new failure on SPARC/Solaris 2.5.1, 2.6 and 7 over RC2: http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00137.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00138.html http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00139.html WARNING: program timed out. FAIL: 21_strings/basic_string/cons/char/1.cc execution test try { std::string str03(csz01 - 1, 'z'); --- stuck here VERIFY( str03.size() != 0 ); VERIFY( str03.size() = str03.capacity() ); } // NB: bad_alloc is regrettable but entirely kosher for // out-of-memory situations. catch(std::bad_alloc fail) { VERIFY( true ); } catch(...) { VERIFY( false ); } The machines are apparently stuck in 'wmemset' from libc initializing str03, which is a bg object: csz01 = str01.max_size(); This didn't happen in RC2 and I've not investigated what changed. The code is the same on Solaris 7 and 8, but the Solaris 2.5.1, 2.6 and 7 machines are substantially more limited than the Solaris 8, 9 and 10 machines. -- Eric Botcazou