From: Mumit Khan <khan@xraylith.wisc.edu>
To: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: Andris Pavenis <pavenis@lanet.lv>,
djgpp-workers@delorie.com, egcs@cygnus.com
Subject: Re: egcs and exceptions
Date: Fri, 30 Oct 1998 14:39:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.981030154313.1576D-100000@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <orpvbbt1mq.fsf@araguaia.dcc.unicamp.br>
On 29 Oct 1998, Alexandre Oliva wrote:
>
> Of course one may argue that libgcc has nothing to do with `the entire
> application', and I'm not really sure you must really choose sjlj at
> build time, but if you have spare CPU cycles to try that, it would be
> nice to know...
With my stock egcs-1.1b setup on i686-pc-linux-gnu, I can turn on sjlj
EH with -fsjlj-exceptions flag, at least for the trivial testcases I've
tried.
This is the first I've heard of sjlj EH not work on a "well greased"
target like i686-linux. In fact, it's the one that consistently works,
where dwarf2 requires a *lot* more work, including cooperation from
the linker. I never did get dwarf2 to work under win32 for example,
but sjlj worked like a champ out of the box the first time.
Regards,
Mumit
next prev parent reply other threads:[~1998-10-30 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-22 5:46 Andris Pavenis
1998-10-30 3:25 ` Alexandre Oliva
1998-10-30 14:39 ` Mumit Khan [this message]
[not found] ` <orpvbbt1mq.fsf.cygnus.egcs@araguaia.dcc.unicamp.br>
1998-10-31 2:52 ` Jason Merrill
1998-10-31 5:02 ` Alexandre Oliva
1998-11-02 22:42 ` Jason Merrill
1998-11-03 6:36 ` Alexandre Oliva
1998-11-04 2:20 Klaus-Georg Adams
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=Pine.SUN.3.93.981030154313.1576D-100000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=djgpp-workers@delorie.com \
--cc=egcs@cygnus.com \
--cc=oliva@dcc.unicamp.br \
--cc=pavenis@lanet.lv \
/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).