User Details
- User Since
- Oct 21 2016, 3:46 AM (233 w, 1 d)
Sat, Mar 13
I have updated the full patch along with the cost model. I have also shared the perf numbers for SPEC CPU 2017 benchmarks in Graviton2 with various modes of optimization enabled :
Mar 5 2021
Feb 20 2021
Feb 4 2021
Feb 2 2021
Move SCCPSolver to new header and .cpp file.
Jan 27 2021
Jan 7 2021
ping!
ping!
Dec 27 2020
Dec 23 2020
Dec 8 2020
Nov 9 2020
Oct 29 2020
Oct 27 2020
Oct 26 2020
Oct 15 2020
I will try to summarize the current changes done in the below C code and also try to answer some of the common questions raised.
ping!
Oct 14 2020
Oct 13 2020
Can you also run the update_llc_test_checks.py script on the file and pre-commit the tests, just showing the changes here.
Sure. I have created new patch : https://reviews.llvm.org/D89365
ping!
Oct 11 2020
Adding support for SABD patterns..
Oct 10 2020
Add support for all integer types.
Oct 9 2020
Oct 8 2020
Oct 7 2020
Fixed review comments
Moved back to https://reviews.llvm.org/D88742
Oct 6 2020
What part of sadb are you worried about? I thought they could be treated the same, given you are extended from enough extra bits. But I may be mistaken, they can be somewhat difficult.
This change seems to be generating a different pattern (UABDLv4i32_v2i64 vs UABDLv2i32_v2i64) for one of the test cases in arm64-vabs.ll. I am not sure whether the new pattern generated is correct and better.
Yes.
Oct 5 2020
The CFG after the optimization of a typical loop will be as follows:
Oct 2 2020
I can certainly commit this. I just need an author string to attribute it correctly. Is "Vinay Madhusudan <vinay@compilertree.com>" OK for that?
The build failure is unrelated to this patch and happening in other patches as well (Example: https://reviews.llvm.org/D88471). What should I do? Also, I do not have commit access. Can you please help in committing this patch?
Oct 1 2020
Fixed context and review comments
Added support for SDOT