diff options
| author | Robert Dazi <14996868+v01dXYZ@users.noreply.github.com> | 2024-09-15 13:48:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-15 15:48:36 +0400 |
| commit | 8837898b8dc34cfa21ba877832a5865af06f52c9 (patch) | |
| tree | 033ed26cf9377fedbbec477a738dd5365c8335a8 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp | |
| parent | 5910e8d6075648d941c5723eab856c58857e345d (diff) | |
| download | llvm-8837898b8dc34cfa21ba877832a5865af06f52c9.zip llvm-8837898b8dc34cfa21ba877832a5865af06f52c9.tar.gz llvm-8837898b8dc34cfa21ba877832a5865af06f52c9.tar.bz2 | |
[DAGCombine] Count leading ones: refine post DAG/Type Legalisation if promotion (#102877)
This PR is related to #99591. In this PR, instead of modifying how the
legalisation occurs depending on surrounding instructions, we refine
after legalisation.
This PR has two parts:
* `SDPatternMatch/MatchContext`: Modify a little bit the code to match
Operands (used by `m_Node(...)`) and Unary/Binary/Ternary Patterns to
make it compatible with `VPMatchContext`, instead of only `m_Opc`
supported. Some tests were added to ensure no regressions.
* `DAGCombiner`: Add a `foldSubCtlzNot` which detect and rewrite the
patterns using matching context.
Remaining Tasks:
- [ ] GlobalISel
- [ ] Currently the pattern matching will occur even before
legalisation. Should I restrict it to specific stages instead ?
- [ ] Style: Add a visitVP_SUB ?? Move `foldSubCtlzNot` in another
location for style consistency purpose ?
@topperc
---------
Co-authored-by: v01dxyz <v01dxyz@v01d.xyz>
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp')
0 files changed, 0 insertions, 0 deletions