From: Alex Bradbury Date: Tue, 14 Mar 2023 19:52:32 +0000 (+0000) Subject: [clang][docs] Clarify the semantics of -fexceptions X-Git-Tag: upstream/17.0.6~14825 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f47404b012d66ed0b411a2b3742931a14e85c80b;p=platform%2Fupstream%2Fllvm.git [clang][docs] Clarify the semantics of -fexceptions As noted in , the documentation for -fexceptions appears to imply that unwind information is always generated, which isn't the case. Differential Revision: https://reviews.llvm.org/D145564 --- diff --git a/clang/docs/CommandGuide/clang.rst b/clang/docs/CommandGuide/clang.rst index 7fae1b5cec53..e076818697eb 100644 --- a/clang/docs/CommandGuide/clang.rst +++ b/clang/docs/CommandGuide/clang.rst @@ -473,8 +473,10 @@ Code Generation Options .. option:: -fexceptions - Enable generation of unwind information. This allows exceptions to be thrown - through Clang compiled stack frames. This is on by default in x86-64. + Allow exceptions to be thrown through Clang compiled stack frames (on many + targets, this will enable unwind information for functions that might have + an exception thrown through them). For most targets, this is enabled by + default for C++. .. option:: -ftrapv