search for: ltod

...e same as we've had elsewhere in LLVM- is there a defined visibility boundary between user and library code? The same problem can be seen in the Malloc attribute annotations (I forget the attribute name) that Vaiva created - having one arbitrary visibility barrier breaks down when libraries are LTOd (bare metal or OpenCl systems being examples) Norecurse as a concept is a trade off between ease of inference and ease of definition. Norecurse is indeed hard for the compiler to infer, but the definition is precise. There may be other, superior options - suggestions welcome! :) Cheers, James O...

https://bugzilla.samba.org/show_bug.cgi?id=13061 Bug ID: 13061 Summary: File lost on case-insensitive file system Product: rsync Version: 3.1.3 Hardware: All OS: Windows 7 Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org

I think the conceptual issues have largely been sorted out, it is mostly that it is *much* harder to deduce norecurse than it might seem like superficially. On Mon, Mar 21, 2016 at 4:02 PM Mehdi Amini <mehdi.amini at apple.com> wrote: > On Mar 21, 2016, at 3:57 PM, Sanjin Sijaric via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Hi, > > GlobalOpt may not