diff options
| author | Aaron Ballman <aaron@aaronballman.com> | 2020-03-26 08:07:21 -0400 |
|---|---|---|
| committer | Aaron Ballman <aaron@aaronballman.com> | 2020-03-26 08:08:23 -0400 |
| commit | 4778e409de112dc4b70933f3e3f502d6c747ed5a (patch) | |
| tree | ce94ba74739f61fd56c9d3fe87e5db19b4872937 /clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp | |
| parent | 076773253ebf17acacc4213c12a9fd88e266705a (diff) | |
| download | llvm-4778e409de112dc4b70933f3e3f502d6c747ed5a.zip llvm-4778e409de112dc4b70933f3e3f502d6c747ed5a.tar.gz llvm-4778e409de112dc4b70933f3e3f502d6c747ed5a.tar.bz2 | |
Clarify use of llvm_unreachable in the coding standard.
There has been some ongoing confusion regarding when to use `llvm_unreachable`
which this patch attempts to address. Specifically, the confusion has been
around whether `llvm_unreachable` is intended to mark only unreachable code
paths that the compiler cannot determine itself or to mark a code path which is
unconditionally a bug to reach. Based on email and IRC discussions, it sounds
like "unconditional bug to reach" is the consensus.
Diffstat (limited to 'clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions