From 4381020e03767cd344c2656ce7e901ea3420d6a6 Mon Sep 17 00:00:00 2001 From: Jason Merrill Date: Mon, 26 Sep 2005 23:11:28 -0400 Subject: [PATCH] * doc/invoke.texi: Clarify documentation of -fno-enforce-eh-specs. From-SVN: r104681 --- gcc/ChangeLog | 4 ++++ gcc/doc/invoke.texi | 11 +++++++---- 2 files changed, 11 insertions(+), 4 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 318e35be23a..de070de522b 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2005-09-26 Jason Merrill + + * doc/invoke.texi: Clarify documentation of -fno-enforce-eh-specs. + 2005-09-26 James E Wilson * config/ia64/crtbegin.asm, config/ia64/crtend.asm: Remove glibc diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 5c8f51ac595..814d9d87958 100644 --- 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 -- 2.30.2