> From: Rainer Orth <r...@cebitec.uni-bielefeld.de> > Date: Thu, 3 Nov 2011 14:10:50 +0100
> Hans-Peter Nilsson <hans-peter.nils...@axis.com> writes: > > > For big changes such as this, please test on a cross > > configuration as well. > > A random cross wouldn't help, and I'd claim it's impractical to set up > full cross environments for all affected targets. I beg to differ on both accounts. A single cross would have provided a smoke-test and once a *-elf is set up, you can reuse that for other *-elf (or *-eabi) targets as well. As Bernd mentioned, newlib, binutils - and sim are all that's needed; different --target=* options and different RUNTESTFLAGS=--target_board=* options. See simtest-howto.html. > That's why I > repeatedly send calls for testers, with exactly no reaction at > all ;-( But isn't that a clue? Looking in my mail, I see a stream of patches from Aug 15, which I reviewed. I don't see anything CC:ed to me after Aug 16 until yesterday. > > For cris-elf, a patch in the range 180770:180778 supposedly > > yours, cause massive testsuite failures on the form of not > > finding functions in libgcc at link-time. From gcc.log: > > > > Executing on host: /tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/xgcc > > -B/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/ > > /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.c-torture/execute/builtins/complex-1.c > > > > /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.c-torture/execute/builtins/complex-1-lib.c > > > > /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c > > -w -O0 -isystem > > /tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/targ-include > > -isystem /tmp/hpautotest-gcc1/gcc/newlib/libc/include > > -B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libgloss/cris/ > > -L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libgloss/cris > > -L/tmp/hpautotest-gcc1/gcc/libgloss/cris > > -B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/ > > -L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib -sim3 -lm -o > > /tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/gcc/complex-1.x0 > > (timeout = 300) > > /tmp/ccAbw5Fs.o: In function `main_test': > > complex-1.c:(.text+0x9e): undefined reference to `__nesf2' > > complex-1.c:(.text+0xb8): undefined reference to `__nesf2' > > complex-1.c:(.text+0xfa): undefined reference to `__nesf2' > > complex-1.c:(.text+0x114): undefined reference to `__nesf2' > > complex-1.c:(.text+0x142): undefined reference to `__nesf2' > > /tmp/ccAbw5Fs.o:complex-1.c:(.text+0x162): more undefined references to > > `__nesf2' follow > > Do you have an old build lying around to check where that symbol came > from before libgcc.a ... > and why that object isn't built any longer/not included > libgcc? Ah, the bug? Nm, I'll go fix it myself. (This is the kind of back-and-forth that's just so time-consuming that I'd rather not. Film at 11.) brgds, H-P
