Displaying 3 results from an estimated 3 matches for "getcallcost".
2016 Mar 10
3
[RFC] Target-specific parametrization of function inliner
...we customize loop unrolling. Use it to provide inliner with
> > target-specific thresholds and other parameters.
> > * augment Inliner pass to use existing TargetTransformInfo API to
> > figure out cost of particular call on a given target.
> > TargetTransforInfo already has getCallCost(), though it does not
> > look like anything uses it.
> >
> >
> > Comments? Concerns? Suggestions?
> >
>
> Hi Art,
>
> I've long thought that we should have a more principled way of doing
> inline profitability. There is obviously some cost to execut...
2016 Apr 01
2
[RFC] Target-specific parametrization of function inliner
...his operation is not legal on this type and will be expanded in multiple instructions in SDAG, too bad..).
--
Mehdi
>
> Set aside what we need longer term for the inliner, the GPU specific problems can be addressed by
> 1) if the call overhead is really large, define a target specific getCallCost and subtract it from the initial Cost when analyzing a callsite (this will help boost all targets with high call costs)
> 2) if not, but instead GPU users can tolerate large code growth, then it is better to this by adjusting the threshold -- perhaps have a user level option -finline-limit=?
>...
2016 Mar 02
3
[RFC] Target-specific parametrization of function inliner
...etTransformInfo in a way similar to how we
customize loop unrolling. Use it to provide inliner with target-specific
thresholds and other parameters.
* augment Inliner pass to use existing TargetTransformInfo API to figure
out cost of particular call on a given target. TargetTransforInfo already
has getCallCost(), though it does not look like anything uses it.
Comments? Concerns? Suggestions?
Thanks,
--
--Artem Belevich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160301/e371ce52/attachment.html>