From: Alexandre Oliva <aoliva@redhat.com>
To: Joe Buck <jbuck@synopsys.COM>
Cc: max@e-soft.ru (Maxim Dementiev), gcc@gcc.gnu.org
Subject: Re: Using throw(): to use or not to use?
Date: Wed, 21 Nov 2001 16:42:00 -0000 [thread overview]
Message-ID: <ork7w9sb2v.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Joe Buck's message of "Thu, 29 Nov 2001 09:35:14 -0800 (PST)"
On Nov 29, 2001, Joe Buck <jbuck@synopsys.COM> wrote:
> Specififying throw() should, if anything, make it possible to generate
> slightly faster code.
Unless you're talking about the function marked as throw() itself,
with an EH model such as setjmp(). This would require the function to
set up handlers that would call unexpected() should the function throw
or propagate some inappropriate exception.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
WARNING: multiple messages have this Message-ID
From: Alexandre Oliva <aoliva@redhat.com>
To: Joe Buck <jbuck@synopsys.COM>
Cc: max@e-soft.ru (Maxim Dementiev), gcc@gcc.gnu.org
Subject: Re: Using throw(): to use or not to use?
Date: Thu, 29 Nov 2001 10:11:00 -0000 [thread overview]
Message-ID: <ork7w9sb2v.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
Message-ID: <20011129101100.vhDwV1thKmT5yFjkNjy7BTiPZNZEfpt4YFnTNR4fWEg@z> (raw)
In-Reply-To: <200111291735.JAA05491@atrus.synopsys.com>
On Nov 29, 2001, Joe Buck <jbuck@synopsys.COM> wrote:
> Specififying throw() should, if anything, make it possible to generate
> slightly faster code.
Unless you're talking about the function marked as throw() itself,
with an EH model such as setjmp(). This would require the function to
set up handlers that would call unexpected() should the function throw
or propagate some inappropriate exception.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-11-29 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 13:56 Maxim Dementiev
2001-11-21 16:00 ` Joe Buck
2001-11-21 16:42 ` Alexandre Oliva [this message]
2001-11-21 22:52 ` Joe Buck
2001-11-29 11:51 ` Joe Buck
2001-11-29 10:11 ` Alexandre Oliva
2001-11-21 23:32 ` Frank Ch. Eigler
2001-11-21 23:42 ` Joe Buck
2001-11-29 13:46 ` Joe Buck
2001-11-29 12:59 ` Frank Ch. Eigler
2001-11-22 13:51 ` Using throw(): continue with "simple code" Maxim Dementiev
2001-11-30 0:04 ` Maxim Dementiev
2001-11-29 9:35 ` Using throw(): to use or not to use? Joe Buck
2001-11-29 5:13 ` Maxim Dementiev
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=ork7w9sb2v.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.COM \
--cc=max@e-soft.ru \
/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).