gcc-3.3 blowing up on ppc405 in _nl_load_domain?

[Dan Kegel]

I successfully built cross-toolchains targeting ppc750 and sh4, and
passed basic gcc remote execution regression tests.
ppc405, however, barfs on all executables built with this
toolchain.

To debug the problem, I built everything static, and ran a test case under gdbserver.
It showed:

Program received signal SIGILL, Illegal instruction.
0x10010b5c in _nl_load_domain ()
(gdb) bt
#0  0x10010b5c in _nl_load_domain ()
#1  0x1000cd10 in _dl_new_object ()
#2  0x1000cd74 in _dl_signal_error ()
#3  0x1000048c in __libc_start_main ()

Annoyingly, binutils, gcc, and glibc all include the source for
nl_load_domain() so it's a bit hard to figure out which one is at fault,
but I'll bet it's the one in gcc.

I think I just found me a reason to add --disable-nls to crosstool's gcc configure line...
on embedded systems, msgcats just get in the way, besides adding bloat.
I'm sure whatever compiler bug/misconfiguration caused the fault will now pop up
somewhere else, but if I'm lucky it'll be in gcc testcase code rather
than standard support startup code.

Onwards and upwards...
- Dan


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com