Following the discussion on parisc, I uploaded glibc built with
gcc-3.4. Validated, that gcc-4.0 bootstraps again and the python build
errors are gone.
Please make this change for the next sourceful upload.
Matthias
> Following the discussion on parisc, I uploaded glibc built with > gcc-3.4. Validated, that gcc-4.0 bootstraps again and the python build > errors are gone. Does this fix GCC PR 23731? Dave -- -- J. David Anglin dave.anglin <at> nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
John David Anglin writes: > > Following the discussion on parisc, I uploaded glibc built with > > gcc-3.4. Validated, that gcc-4.0 bootstraps again and the python build > > errors are gone. > > Does this fix GCC PR 23731? down to 475 test failures. Maybe related to PR23602
> John David Anglin writes: > > > Following the discussion on parisc, I uploaded glibc built with > > > gcc-3.4. Validated, that gcc-4.0 bootstraps again and the python build > > > errors are gone. > > > > Does this fix GCC PR 23731? > > down to 475 test failures. Maybe related to PR23602 I suspect that there are still glibc issues. With 2.3.2.ds1-22, I don't see anywhere this number of fails: http://gcc.gnu.org/ml/gcc-testresults/2005-09/msg00946.html. >From testing with 4.1, I know that the SyncTest and Thread_Monitor can be fixed by adding locking to the pa compare_and_swap implementation for java. This is important on SMP systems. I made a couple of changes to libjava on head which fixed problems with java exception handling on the pa: 2005-08-21 John David Anglin <dave.anglin <at> nrc-cnrc.gc.ca> PR libgcj/23507 * stacktrace.cc (_Jv_StackTrace::UnwindTraceFn): Fix typo in newLength assignment. Cast operands of compare to function pointer type. 2005-08-20 John David Anglin <dave.anglin <at> nrc-cnrc.gc.ca> PR libgcj/21692 * sysdep/pa/descriptor.h: New file.(Continue reading)
John David Anglin writes: > > Following the discussion on parisc, I uploaded glibc built with > > gcc-3.4. Validated, that gcc-4.0 bootstraps again and the python build > > errors are gone. > > Does this fix GCC PR 23731? can't check, it currently segfaults trying to generate the classmap.db (same thing already happens with 4.0 on m68k-linux). $ gdb .libs/gcj-dbtool GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "hppa-linux"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) set args -n foo.db (gdb) run Starting program: /scratch/packages/gcc/snap/gcc-snapshot-20050919/build/hppa-linux-gnu/libjava/.libs/gcj-dbtool -n foo.db [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 4227)] [New Thread 32769 (LWP 4230)] [New Thread 16386 (LWP 4231)] Program received signal SIGSEGV, Segmentation fault.(Continue reading)
RSS Feed