search for: okay'd

...hieved with empty inline asms, however they tend > to pessimize optimizations. The patch above allows all of the major > optimizations to work in the presence of @llvm.sideeffect. > > > I think that we should move forward with this approach (as may be obvious > given that I've okay'd the patch). It's a lightweight solution, at least on > LLVM's side of things, and does not prevent other solutions later. > > > One of the concerns raised is that front-ends would have to emit a lot of > these intrinsics, potentially one in every loop, one in every func...

Hello, This email picks up the thread that to my knowledge was last discussed here: http://lists.llvm.org/pipermail/llvm-dev/2015-July/088103.html In brief, infinite loops containing no side effects produce undefined behavior in C++ (and C in some cases), however in other languages, they have fully defined behavior. LLVM's optimizer currently assumes that infinite loops eventually terminate