Mark Mitchell <[EMAIL PROTECTED]> writes:

> RC2 is available here:
> 
>   ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.0-20050417/
> 
> As before, I'd very much appreciate it if people would test these bits
> on primary and secondary platforms, post test results with the
> contrib/test_summary script, and send me a message saying whether or
> not there are any regressions, together with a pointer to the results.

Bad news, I'm afraid.

On powerpc-darwin8, this fails to bootstrap, with an ICE in libjava (when
trying to build gnu-xml.o).

The backtrace is:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
fold_convert (type=0x4160c380, arg=0x0) at 
/Network/Servers/hills/Volumes/capanna/gkeating/co/gcc-4.0.0-20050417/gcc/fold-const.c:1886
1886      tree orig = TREE_TYPE (arg);
(gdb) bt
#0  fold_convert (type=0x4160c380, arg=0x0) at 
/Network/Servers/hills/Volumes/capanna/gkeating/co/gcc-4.0.0-20050417/gcc/fold-const.c:1886
#1  0x0028c5b4 in bit_from_pos (offset=0x28c5b4, bitpos=0x0) at 
/Network/Servers/hills/Volumes/capanna/gkeating/co/gcc-4.0.0-20050417/gcc/stor-layout.c:542
#2  0x00118438 in dbxout_type (type=0x42434680, full=0) at 
/Network/Servers/hills/Volumes/capanna/gkeating/co/gcc-4.0.0-20050417/gcc/dbxout.c:1392

The type involved is:

 <field_decl 0x48c6d280 code
    type <integer_type 0x4160c500 short public HI
        size <integer_cst 0x4160e500 constant invariant 16>
        unit size <integer_cst 0x4160e520 constant invariant 2>
        align 16 symtab 52 alias set 15 precision 16 min <integer_cst 
0x4160e4a0 -32768> max <integer_cst 0x4160e4c0 32767>
        pointer_to_this <pointer_type 0x41665e00> chain <type_decl 0x4160c580 
short>>
    ignored decl_1 VOID file gnu/xml/dom/DomElement.java line 324
    align 1 offset_align 1 context <record_type 0x42434680 
org.w3c.dom.DOMException> chain <field_decl 0x425bd180 D.4079>>

I'll run another build with a patch applied to disable libgcj on
ppc-darwin, and see how that goes.  I'll also try to work out which
patch broke it.

Reply via email to