search for: visitallocsite

...s road is superior to the inaccessiblememonly when it come to memory allocation for the following reason: - If the allocator can be exposed (custom allocator use case) inaccessiblememonly is not usable while this is. - Other allocation related optimizations can kick in (for instance InstCombiner::visitAllocSite). I think it is fair to keep this attribute for the managed language use case, for instance, to improve GlobalsAA, but we should definitively restrict it to function that are declared but NOT defined. When merging modules, if a function with the attribute becomes defined, then it needs to be throw...

2015-12-26 18:32 GMT+01:00 Philip Reames <listmail at philipreames.com>: > On 12/26/2015 02:17 AM, Amaury SECHET via llvm-dev wrote: > > I'm trying to fix that bug: https://llvm.org/bugs/show_bug.cgi?id=20049 > > It turns out this is the kind of optimization that I really need, as when > it isn't done, all kind of other optimizations opportunities down the road