public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Perry Smith <pedz@easesoftware.com>
Cc: MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: Exception Specifications
Date: Wed, 06 Dec 2006 15:12:00 -0000	[thread overview]
Message-ID: <m3ac213vp2.fsf@localhost.localdomain> (raw)
In-Reply-To: <4B2BA253-38ED-423C-8DC1-21DC7DE2FFDC@easesoftware.com>

Perry Smith <pedz@easesoftware.com> writes:

> I believe I saw in some of the boost libraries that they do not use
> exception specifications because some compilers produce slower code.

Adding an exception specification to a function declaration (e.g.,
throw()) should not cause gcc to generate slower code.  In a few cases
it will actually permit gcc to generate faster code.

Ian

  reply	other threads:[~2006-12-06 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 14:27 Perry Smith
2006-12-06 15:12 ` Ian Lance Taylor [this message]
2006-12-06 15:21 ` John Love-Jensen
2006-12-06 15:48   ` Perry Smith
2006-12-06 16:04     ` John Love-Jensen
2006-12-06 14:50 Martin York

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=m3ac213vp2.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=pedz@easesoftware.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).