Displaying 3 results from an estimated 3 matches for "anyrate".
2015 Nov 06
2
[RFC] A new intrinsic, `llvm.blackbox`, to explicitly prevent constprop, die, etc optimizations
On Tue, Nov 3, 2015 at 2:50 PM, Diego Novillo <dnovillo at google.com> wrote:
> I don't see how this is any different from volatile markers on
> loads/stores or memory barriers or several other optimizer blocking
> devices. They generally end up crippling the optimizers without much added
> benefit.
>
Volatile must touch memory (right?). Memory is slow.
> Would it
2015 Nov 06
4
[RFC] A new intrinsic, `llvm.blackbox`, to explicitly prevent constprop, die, etc optimizations
...s far
easier than adding an instruction, and is transparent to optimization
passes. If your added functionality can be expressed as a function call, an
intrinsic function is the method of choice for LLVM extension." (from
http://llvm.org/docs/ExtendingLLVM.html). That sounds perfect to me.
At anyrate, I apologize for my original hand-wavy-ness; I am young and
inexperienced.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151106/7f1d850a/attachment-0001.html>
2015 Nov 03
2
[RFC] A new intrinsic, `llvm.blackbox`, to explicitly prevent constprop, die, etc optimizations
On Mon, Nov 2, 2015 at 9:16 PM, Daniel Berlin <dberlin at dberlin.org> wrote:
> I'm very unclear and why you think a generic black box intrinsic will have
> any different performance impact ;-)
>
>
> I'm also unclear on what the goal with this intrinsic is.
> I understand the symptoms you are trying to solve - what exactly is the
> disease.
>
> IE you say