public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'Tom Quarendon' <tom@quarendon.net>,
	gcc@gcc.gnu.org, 	'gcc help' <gcc-help@gcc.gnu.org>
Subject: Re: Exception handling tables for function generated on the fly
Date: Tue, 12 Aug 2008 18:06:00 -0000	[thread overview]
Message-ID: <48A1CF11.2090608@avtrex.com> (raw)
In-Reply-To: <004401c8fca2$b8980090$9601a8c0@CAM.ARTIMI.COM>

Dave Korn wrote:
> David Daney wrote on 12 August 2008 18:19:
> 
>> Questions like this should probably go to gcc-help@gcc.gnu.org
> 
>   Questions about deep compiler internals and EH abis?  Seems a bit intense
> for the where's-the-any-key list to me...
> 

gcc@ is for questions about development of GCC.

gcc-help@ is for everything else.
.
.
.

>> If you pass -funwind-tables to gcc it will generate the necessary
>> unwinding information. 
.
.
.
>   Yes.  The OP's question is "How do I generate .eh_frame data at runtime
> for an arbitrary function that has no throws and no catches but may call
> functions that throw".
> 

Which is why I recommended passing -funwind-tables, which does exactly that.

David Daney

  reply	other threads:[~2008-08-12 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48A1B059.1040400@quarendon.net>
2008-08-12 17:42 ` David Daney
2008-08-12 17:58   ` Dave Korn
2008-08-12 18:06     ` David Daney [this message]
2008-08-12 18:08       ` David Daney
2008-08-12 18:41       ` Dave Korn

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=48A1CF11.2090608@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=dave.korn@artimi.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=tom@quarendon.net \
    /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).