This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Using throw(): to use or not to use?
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Joe Buck <jbuck at synopsys dot COM>
- Cc: max at e-soft dot ru (Maxim Dementiev), gcc at gcc dot gnu dot org
- Date: 29 Nov 2001 16:09:44 -0200
- Subject: Re: Using throw(): to use or not to use?
- Organization: GCC Team, Red Hat
- References: <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