From: Matthias Klose <doko@cs.tu-berlin.de>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: Bernardo Innocenti <bernie@develer.com>,
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 05:16:00 -0000 [thread overview]
Message-ID: <16478.8118.467796.746467@gargle.gargle.HOWL> (raw)
In-Reply-To: <20040321201636.GA1186@linux-m68k.org>
Richard Zidlicky writes:
> On Sat, Mar 20, 2004 at 04:46:03AM +0100, Bernardo Innocenti wrote:
> lot of the failures may not be failures, too small timeout for
> m68k.
>
> > --enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu
>
> why sjlj exceptions? Is something terribly broken with the other
> exception model?
To be compatible with gcc-3.2, another ABI transition would have
delayed the Debian release process even more ...
Matthias
prev parent reply other threads:[~2004-03-21 23:07 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
2004-03-22 7:48 ` Bernardo Innocenti
2004-03-25 23:25 ` Jim Wilson
2004-03-22 5:16 ` Matthias Klose [this message]
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=16478.8118.467796.746467@gargle.gargle.HOWL \
--to=doko@cs.tu-berlin.de \
--cc=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).