This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
PATCH to doc/invoke.texi for -fno-enforce-eh-specs
- From: Jason Merrill <jason at redhat dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Mon, 26 Sep 2005 23:08:53 -0400
- Subject: PATCH to doc/invoke.texi for -fno-enforce-eh-specs
I recently got a bug report about throwing an exception through a
throw() spec causing the program to abort even with
-fno-enforce-eh-specs. That is, of course, the intended behavior, so
I've tried to clarify the docs a bit.
Applied to trunk.
2005-09-26 Jason Merrill <jason@redhat.com>
* doc/invoke.texi: Clarify documentation of -fno-enforce-eh-specs.
*** doc/invoke.texi.~1~ 2005-09-23 10:41:49.000000000 -0400
--- doc/invoke.texi 2005-09-26 16:48:36.000000000 -0400
*************** call the copy constructor in all cases.
*** 1460,1469 ****
@item -fno-enforce-eh-specs
@opindex fno-enforce-eh-specs
! Don't check for violation of exception specifications at runtime. This
! option violates the C++ standard, but may be useful for reducing code
! size in production builds, much like defining @samp{NDEBUG}. The compiler
! will still optimize based on the exception specifications.
@item -ffor-scope
@itemx -fno-for-scope
--- 1460,1472 ----
@item -fno-enforce-eh-specs
@opindex fno-enforce-eh-specs
! Don't generate code to check for violation of exception specifications
! at runtime. This option violates the C++ standard, but may be useful
! for reducing code size in production builds, much like defining
! @samp{NDEBUG}. This does not give user code permission to throw
! exceptions in violation of the exception specifications; the compiler
! will still optimize based on the specifications, so throwing an
! unexpected exception will result in undefined behavior.
@item -ffor-scope
@itemx -fno-for-scope