From: Dan Gohman Date: Sat, 24 Apr 2010 22:15:58 +0000 (+0000) Subject: PHI nodes also do not necessarily return trap with a trap operand. X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=698cbcb0a4a181d49eca2d6a098e47eef0db96d8;p=oota-llvm.git PHI nodes also do not necessarily return trap with a trap operand. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@102278 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/LangRef.html b/docs/LangRef.html index ac28107bd4b..1142e9290d4 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -2313,8 +2313,8 @@ has undefined behavior.

effects has nevertheless detected a condition which results in undefined behavior.

-

Any non-void instruction or constant expression other than non-intrinsic - calls or invokes with a trap operand has trap as its result value. +

Any non-void instruction or constant expression other than a non-intrinsic + call, invoke, or phi with a trap operand has trap as its result value. Any instruction with a trap operand which may have side effects emits those side effects as if it had an undef operand instead.