m68k-linux regressions

[Bernardo Innocenti]

Richard Zidlicky wrote:

>>The number of failures might look high, but it's much better
>>than I what I got from my previous tests in January (>170
>>failures on m68k-netbsd!).
> 
> lot of the failures may not be failures, too small timeout for
> m68k.

Where do I change Dejagnu's default timeout for the gcc.dg
testsuite?


>>--enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu 
> 
> why sjlj exceptions? Is something terribly broken with the other
> exception model?

I've copied that from the configuation of the system compiler of
the m68k host.  It runs Debian unstable:

Reading specs from /usr/lib/gcc-lib/m68k-linux/3.3.3/specs
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc m68k-linux
Thread model: posix
gcc version 3.3.3 (Debian 20040306)

I'll re-run the tests with DWARF2 exceptions enabled, it would be useful
as a confidence test to debug exceptions on m68k-uclinux, which are still
buggy on the ColdFire.

-- 
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/