Yuri
2010-Jun-05 04:15 UTC
[LLVMdev] Why UnreachableInst instruction is required when the last call has NoReturn flag?
Looks like these two things duplicate each other. Yuri
Eli Friedman
2010-Jun-05 04:56 UTC
[LLVMdev] Why UnreachableInst instruction is required when the last call has NoReturn flag?
On Fri, Jun 4, 2010 at 9:15 PM, Yuri <yuri at rawbw.com> wrote:> Looks like these two things duplicate each other.It's mostly for consistency; every block is required to end in a terminator instruction, and terminator instructions only appear at the end of a basic block. Since "call" is not a terminator instruction, it must be followed by one. -Eli
Reasonably Related Threads
- [LLVMdev] Why variables get "optimized away" after the last use in unoptimized code?
- [LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
- [LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
- [LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
- [LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link