search for: nonbuiltin

...ct to discard it when doing cross-language inlining. It > just becomes something that C-family frontends need to remember to add to > enable their special-case language rules, rather than something that non-C > languages need to think about. Similar to the 'access', builtin vs > nonbuiltin discussion happening in parallel, the attribute enables the > optimization, rather than inhibiting it. > > > As I said below, a function attribute is insufficient. It needs to be > something we can mark per loop. This is needed to correctly model C. The > sideeffect intrinsic is t...

...conservatively correct to discard it when doing cross-language inlining. It just becomes something that C-family frontends need to remember to add to enable their special-case language rules, rather than something that non-C languages need to think about. Similar to the 'access', builtin vs nonbuiltin discussion happening in parallel, the attribute enables the optimization, rather than inhibiting it. On Fri, Oct 27, 2017 at 12:37 PM, Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On 10/27/2017 12:08 AM, Dan Gohman via llvm-dev wrote: > > Hello, > > Thi...

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