From: Ian Lance Taylor <iant@google.com>
To: Andrew Haley <aph@redhat.com>
Cc: Barry Andrews <titanandrews@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: Mixing exception handling libraries with non exception handling
Date: Tue, 05 Aug 2008 14:33:00 -0000 [thread overview]
Message-ID: <m3iqufpm76.fsf@google.com> (raw)
In-Reply-To: <489725F8.5040801@redhat.com> (Andrew Haley's message of "Mon\, 04 Aug 2008 16\:53\:28 +0100")
Andrew Haley <aph@redhat.com> writes:
>> Is there no work around for this? It seems so very strange to me.
>
> Compile with -fexceptions.
Or -funwind-tables.
Ian
next prev parent reply other threads:[~2008-08-05 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 14:40 Barry Andrews
2008-08-04 15:00 ` Andrew Haley
[not found] ` <48971DE4.90804@gmail.com>
2008-08-04 15:26 ` Andrew Haley
[not found] ` <48972282.2060208@gmail.com>
2008-08-04 15:54 ` Andrew Haley
[not found] ` <489728DE.50403@gmail.com>
2008-08-04 16:25 ` Andrew Haley
2008-08-05 14:33 ` Ian Lance Taylor [this message]
[not found] ` <489867BB.1090204@gmail.com>
2008-08-05 15:28 ` Andrew Haley
2008-08-05 16:23 ` Ian Lance Taylor
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=m3iqufpm76.fsf@google.com \
--to=iant@google.com \
--cc=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=titanandrews@gmail.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).