User Details
- User Since
- Sep 10 2021, 3:24 AM (106 w, 1 d)
Thu, Aug 31
@danilaml OrderedRoots has Instructions from the same BasicBlock, and they get there one by one during for (auto &I : *B) iteration. So, there is no risk of messing up there unless someone tries to add much more functionality :)
Wed, Aug 30
Tue, Aug 29
Added tests with different store pointers
Add tests with different store pointers
Ping about the RISC-V conversation and more test requirements
Aug 15 2023
Please make sure to pre-commit test coverage (https://llvm.org/docs/TestingGuide.html#precommit-workflow-for-tests). This is also missing some tests, in particular multi-use and negative tests.
- Added test with @use applied to nested add
- Minor fixes
Added reference to the github issue
Aug 11 2023
Aug 10 2023
Aug 9 2023
Aug 8 2023
Added a test for neoverse-v1
Remove RUN with -mcpu=neoverse-v1 due to too many changes
Rebase after adding extra tests
- Add RUN line to sve-ld1r.ll test with -mcpu=neoverse-v1
- Update feature description
- Add missing Predicate
Aug 7 2023
Renaming
Update CHECK lines
- Rename new feature avoid-ldr1 to no-sve-fp-ld1r
- Now change is applied only to FP LD1R instructions
- Some other renaming inside code
Update CHECK lines
Update test functions names
- Vscale -> VScale
- Move foldVScaleSplatAddSub call to visitAdd and visitSub
- Refactor pattern detection algorithm
Rebase
Remove comment. Update tests to match patterns better
Replace AArch64ptrue 31 pattern with SVEAllActive
Aug 4 2023
@NickGuy, it looks like we had O(2**N) complexity there where N is the depth of identifyNode call stack :)
Aug 3 2023
Added link to GitHub issue
Aug 2 2023
Jul 31 2023
Jul 25 2023
Jul 24 2023
Move code to a separate function and completely refactor it
Jul 19 2023
Jul 18 2023
Update commit message and some tests comments
Jul 14 2023
Jul 13 2023
Move comments from definition to declaration
Address comments
Jul 10 2023
Rebase and update commit message
Jul 7 2023
I adjusted the commit message rather than adding a test. It doesn't matter if vectors are scalable or fixed-width cause code that processes PHINodes does not behave differently. So I think adding a scalable test doesn't add more coverage.
Update test and commit message
Jul 6 2023
Update test and commit message
@glandium, thanks. I've reproduced and prepared the solution - https://reviews.llvm.org/D154598
Jul 5 2023
Jul 4 2023
Jul 3 2023
Jun 29 2023
Add argument name
Jun 28 2023
Ok, then!
Rebase after pre-commit
Jun 27 2023
Forgot to run tests update script
- IsOperationsupported -> IsOperationSupported
- Remove some artefacts