search for: hasnoaccessiblest

...ibleState" is in fact a no-op because it implies nothing about > the *accessible* state. OK, there's inaccessible state but is there or is > there not accessible, visible state, is the question that optimizers need > to ask. > > So I'd rephrase it to something like "HasNoAccessibleState" ? > > James > > On Fri, 4 Dec 2015 at 07:58 Vaivaswatha Nagaraj via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >is this "internal state” supposed to be private to the function? >> It could be private or not. Hence the name "inacces...

>is this "internal state” supposed to be private to the function? It could be private or not. Hence the name "inaccessible", to mean that the program under compilation has no access to the state. So while printf and malloc (for example) could share state in libc, the program under compilation cannot access this state. >how this flag would prevent the last “optimization”