llvm-project.git/llvm/test/Transforms/FunctionSpecialization/function-specialization4.ll, branch users/nico/python-2

[FuncSpec] Enable SpecializeLiteralConstant by default (#113442)

2024-10-29T11:41:25+00:00

Enable specialization on literal constant arguments by default in
Function Specialization.

---------

Co-authored-by: Alexandros Lamprineas

[FuncSpec] Adjust the names of specializations and promoted stack values

2023-09-19T13:40:31+00:00

Currently the naming scheme is a bit funky; the specializations are named
after the original function followed by an arbitrary decimal number. This
makes it hard to debug inlined specializations of recursive functions.
With this patch I am adding ".specialized." in between of the original
name and the suffix, which is now a single increment counter.

[FuncSpec][NFC] Command line option renaming.

2023-03-15T18:03:44+00:00

Standardize all options with 'funcspec' prefix and shorter abreviations.

Differential Revision: https://reviews.llvm.org/D145378

[IPSCCP] Create a Pass parameter to control specialization of functions.

2022-12-23T16:54:45+00:00

Required for D140210 in order to disable FuncSpec at {Os, Oz}
optimization levels.

Differential Revision: https://reviews.llvm.org/D140564

[FuncSpec] Make the Function Specializer part of the IPSCCP pass.

2022-12-10T14:39:49+00:00

Reland 877a9f9abec61f06e39f1cd872e37b828139c2d1 since D138654 (parent)
has been fixed with 9ebaf4fef4aac89d4eff08e48185d61bc893f14e and with
8f1e11c5a7d70f96943a72649daa69f152d73e90.

Differential Revision: https://reviews.llvm.org/D126455

Revert "[FuncSpec] Make the Function Specializer part of the IPSCCP pass."

2022-12-08T12:41:43+00:00

This reverts commit 877a9f9abec61f06e39f1cd872e37b828139c2d1.

It depends on the parent revision 42c2dc401742266da3e0251b6c1ca491f4779963
which needs to be reverted as it broke some buildbots, so reverting both.

[FuncSpec] Make the Function Specializer part of the IPSCCP pass.

2022-12-08T12:14:27+00:00

The aim of this patch is to minimize the compilation time overhead of
running Function Specialization. It is about 40% slower to run as a
standalone pass (IPSCCP + FuncSpec vs IPSCCP with FuncSpec) according
to my measurements. I compiled the llvm testsuite with NewPM-O3 + LTO
and measured single threaded [user + system] time of IPSCCP and FuncSpec
by passing the '-time-passes' option to lld. Then I compared the two
configurations in terms of Instruction Count of the total compilation
(not of the individual passes) as in https://llvm-compile-time-tracker.com.
Geomean for non-LTO builds is -0.25% and LTO is -0.5% approximately.

You can find more info below:

https://discourse.llvm.org/t/rfc-should-we-enable-function-specialization/61518

Differential Revision: https://reviews.llvm.org/D126455

[NFC] Port all FunctionSpecialization tests to `-passes=` syntax

2022-12-07T23:38:43+00:00

FunctionSpecialization: Convert tests to opaque pointers

2022-11-28T14:35:48+00:00

[FuncSpec] Support function specialization across multiple arguments.

2022-03-28T11:01:53+00:00

The current implementation of Function Specialization does not allow
specializing more than one arguments per function call, which is a
limitation I am lifting with this patch.

My main challenge was to choose the most suitable ADT for storing the
specializations. We need an associative container for binding all the
actual arguments of a specialization to the function call. We also
need a consistent iteration order across executions. Lastly we want
to be able to sort the entries by Gain and reject the least profitable
ones.

MapVector fits the bill but not quite; erasing elements is expensive
and using stable_sort messes up the indices to the underlying vector.
I am therefore using the underlying vector directly after calculating
the Gain.

Differential Revision: https://reviews.llvm.org/D119880