From: Bernardo Innocenti <bernie@develer.com>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: GCC Mailing List <gcc@gcc.gnu.org>, Gunther Nikl <gni@gecko.de>,
Jim Wilson <wilson@specifixinc.com>
Subject: Re: m68k-linux regressions
Date: Mon, 22 Mar 2004 04:30:00 -0000 [thread overview]
Message-ID: <405E0C27.1010102@develer.com> (raw)
In-Reply-To: <20040321201636.GA1186@linux-m68k.org>
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/
next prev parent reply other threads:[~2004-03-21 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 6:48 Bernardo Innocenti
2004-03-22 1:27 ` Richard Zidlicky
2004-03-22 4:30 ` Bernardo Innocenti [this message]
2004-03-22 7:48 ` Bernardo Innocenti
2004-03-25 23:25 ` Jim Wilson
2004-03-22 5:16 ` Matthias Klose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=405E0C27.1010102@develer.com \
--to=bernie@develer.com \
--cc=gcc@gcc.gnu.org \
--cc=gni@gecko.de \
--cc=rz@linux-m68k.org \
--cc=wilson@specifixinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).