* doc/invoke.texi: Clarify documentation of -fno-enforce-eh-specs.
From-SVN: r104681
This commit is contained in:
parent
4bd2f9d6a1
commit
4381020e03
2 changed files with 11 additions and 4 deletions
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue