Bootstrap problems on VAX with gcc-current.

[Matt Thomas <matt at 3am-software dot com>]

[There's been a related bug report on this that was sent to gcc-bugs; see
http://gcc.gnu.org/ml/gcc-bugs/2002-08/msg00668.html for that report.  The
example in that report fails identically on VAX.]

The problem happens when compiling unwind-dw2-fde.c so I added two calls
to debug_rtx to print the "x" and "in" rtl's when reg_overlap_mentioned_p
abort()'s.

./xgcc -B./ -B/usr/local/vax-netbsdelf/bin/ -isystem 
/usr/local/vax-netbsdelf/include -isystem 
/usr/local/vax-netbsdelf/sys-include -O2  -DIN_GCC -DCROSS_COMPILE   -W 
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem 
./include   -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. 
-I. -I/export/toolchain/gcc/gcc -I/export/toolchain/gcc/gcc/. 
-I/export/toolchain/gcc/gcc/config -I/export/toolchain/gcc/gcc/../include 
-fexceptions -c /export/toolchain/gcc/gcc/unwind-dw2-fde.c -o 
libgcc/./unwind-dw2-fde.o
In file included from /export/toolchain/gcc/gcc/unwind-dw2-fde.c:37:
/export/toolchain/gcc/gcc/unwind-pe.h: In function `size_of_encoded_value':
/export/toolchain/gcc/gcc/unwind-pe.h:76: warning: implicit declaration of 
function `abort'
/export/toolchain/gcc/gcc/unwind-dw2-fde.c: In function `get_cie_encoding':
/export/toolchain/gcc/gcc/unwind-dw2-fde.c:271: warning: implicit 
declaration of function `strlen'
(zero_extract:SI (mem/s:QI (plus:SI (reg/v/f:SI 21)
            (const_int 17 [0x11])) [0 S1 A8])
    (const_int 21 [0x15])
    (const_int 3 [0x3]))
(set (pc)
    (if_then_else (eq (cc0)
            (const_int 0 [0x0]))
        (label_ref 74)
        (pc)))
/export/toolchain/gcc/gcc/unwind-dw2-fde.c: In function `init_object':
/export/toolchain/gcc/gcc/unwind-dw2-fde.c:924: internal compiler error: in 
reg_overlap_mentioned_p, at rtlanal.c:1545
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

The problem is that reg_overlap_mentioned_p doesn't handle zero_extract.  Now
the question is: should it?  Or was should it never have been passed a
zero_extract pattern?

I'd like to get some progress made on the VAX toolchain.  But it seems to
be suffering from frequent collateral damage.  Sigh.

--
Matt Thomas               Internet:   matt@3am-software.com
3am Software Foundry      WWW URL:    http://www.3am-software.com/bio/matt/
Cupertino, CA             Disclaimer: I avow all knowledge of this message