[llvm-dev] [RFC] Adding target-specific overrides for Indirect Call Promotion
Finkel, Hal J. via llvm-dev
llvm-dev at lists.llvm.org
Thu Aug 22 22:54:42 PDT 2019
Am I correct in assuming that the reason it makes sense for these to be target dependent is because there's on the dependence on the relative cost of checks vs. the indirect-call overhead? There's also a different from other inlining benefits, but I imagine that's more-weakly target dependent.
To what would you like to change the max-annotations value? Should this always match the max-prom value?
On 8/22/19 10:50 AM, Wael Yehia via llvm-dev wrote:
We see improved performance on the PowerPC platform by increasing the aggressiveness of Indirect Call Promotion (ICP).
In particular, lowering the promotion threshold and increasing the maximum number of promotions helps.
The following command line options (default values shown) control some of the ICP parameters:
We would like to change their defaults to a target specific value.
I have few questions:
1. Is anyone else interested in having target specific default values for the above options?
2. Is anyone against making the defaults for the above options target dependent?
3. If I were to make the default values target dependent (but allow user specified option to trump the defaults) the question is whether the following is the best and simplest way to do it:
- teach `TargetTransformInfo` (TTI) about the above 3 values (basically add 3 integer-returning query functions).
- make `PGOinstrumentationUse`, `PGOIndirectCallPromotion`, and `ModuleSummaryIndexAnalysis` passes require the `TargetIRAnalysis` pass so that they can access the TTI instance, and pass it to `ICallPromotionAnalysis`.
The legacy PM passes would be changed symmetrically.
IBM Canada Lab
wyehia at ca.ibm.com<mailto:wyehia at ca.ibm.com>
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev