> 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  <[EMAIL PROTECTED]>

        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  <[EMAIL PROTECTED]>

        PR libgcj/21692
        * sysdep/pa/descriptor.h: New file.
        * configure.host: Use sysdep/pa/descriptor.h on hppa*-*.

Possibly, we need to look at back porting these fixes.  However,
the code in 4.0 is different and I wasn't seeing the same errors.

Dave
-- 
J. David Anglin                                  [EMAIL PROTECTED]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to