* doc/invoke.texi: Clarify documentation of -fno-enforce-eh-specs.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@104681 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 318e35b..de070de 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2005-09-26  Jason Merrill  <jason@redhat.com>
+
+       * doc/invoke.texi: Clarify documentation of -fno-enforce-eh-specs.
+
 2005-09-26  James E Wilson  <wilson@specifix.com>
 
        * config/ia64/crtbegin.asm, config/ia64/crtend.asm: Remove glibc

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 5c8f51a..814d9d8 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -1460,10 +1460,13 @@ call the copy constructor in all cases.
 
 @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.
+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