6 Commits

Author	SHA1	Message	Date
Chuanqi Xu	16bf4a4717	[FuncSpec] Add an option to specializing literal constant ... Now the option is off by default. Since we are not sure if this option would make the compile time increase aggressively. Although we tested it on SPEC2017, we may need to test more to make it on by default. Reviewed By: SjoerdMeijer Differential Revision: https://reviews.llvm.org/D104365	2021-06-30 11:26:44 +08:00
Sjoerd Meijer	a6fd3be6d5	[FuncSpec] Don't specialise functions with NoDuplicate instructions. ... getSpecializationCost was returning INT_MAX for a case when specialisation shouldn't happen, but this wasn't properly checked if specialisation was forced. Differential Revision: https://reviews.llvm.org/D104461	2021-06-21 09:02:11 +01:00
Sjoerd Meijer	467b51294d	[FuncSpec] Don't specialise functions with attribute NoDuplicate. ... Differential Revision: https://reviews.llvm.org/D104378	2021-06-17 10:32:29 +01:00
Sjoerd Meijer	f03e6d3f6e	[FuncSpec] Statistics ... Adds some bookkeeping for collecting the number of specialised functions and a test for that. Differential Revision: https://reviews.llvm.org/D104102	2021-06-16 09:11:51 +01:00
Chuanqi Xu	2821a035e7	[FuncSpec] Use std::pow instead of operator^ ... The original implementation calculating UserBonus uses operator ^, which means XOR in C++ language. At the first glance of reviewing, I thought it should be power, my bad. It doesn't make sense to use XOR here. So I believe it should be a carelessness as I made. Test Plan: check-all Reviewed By: SjoerdMeijer Differential Revision: https://reviews.llvm.org/D104282	2021-06-16 10:13:21 +08:00
Sjoerd Meijer	ee05a3e562	Move Function Specialization to its correct location. NFC. ... As a follow up of rGc4a0969b9c14, and as part of D104102, move it to the IPO transformations directory.	2021-06-11 15:00:10 +01:00