From: Jason Merrill <jason@cygnus.com>
To: robertl@dgii.com (Robert Lipe), egcs@cygnus.com
Subject: Re: controlling exception type per target
Date: Wed, 01 Oct 1997 19:22:00 -0000 [thread overview]
Message-ID: <u9pvpo29bg.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <19970928233930.41615.cygnus.egcs@dgii.com>
Sorry I haven't gotten back to you before. I think this should be handled
by setting up exceptions_via_longjmp in main(), with a simple
#ifdef DWARF2_UNWIND_INFO
exceptions_via_longjmp = DWARF2_UNWIND_INFO;
#endif
> Should I expand this scheme on into crtstuff as well?
You can tell whether you are doing COFF or ELF with #ifdefs, right? I
would think you could special-case the SCO tm.h so that when CRT_BEGIN or
CRT_END are defined, you use unconditional defines. irix6.h does something
similar for n32/n64 multilibbing.
Jason
next prev parent reply other threads:[~1997-10-01 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-25 10:31 Robert Lipe
1997-09-28 21:41 ` Robert Lipe
[not found] ` <19970928233930.41615.cygnus.egcs@dgii.com>
1997-10-01 19:22 ` Jason Merrill [this message]
1997-10-01 23:00 ` Patches for egcs/OSR5 Was: " Robert Lipe
1997-10-01 23:33 ` Jason Merrill
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=u9pvpo29bg.fsf@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=egcs@cygnus.com \
--cc=robertl@dgii.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).