diff options
| author | Sebastian Pop <spop@nvidia.com> | 2025-11-20 16:50:37 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-11-20 16:50:37 -0600 |
| commit | 70311b453c73c8bc92362bb4035449f3a87210fc (patch) | |
| tree | d4689abecb13c4f35bf3287a0d1fc6ac7aff43c8 /lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedProcessPythonInterface/ScriptedProcessPythonInterface.h | |
| parent | b83e458fe5330227581e1e65f3866ddfcd597837 (diff) | |
[unroll-and-jam] Document dependency patterns in dependencies.ll (NFC) (#156577)
Add detailed comments explaining each function's memory access patterns
and why they should/shouldn't be unroll-and-jammed:
- fore_aft_*: Dependencies between fore block and aft block
- fore_sub_*: Dependencies between fore block and sub block
- sub_aft_*: Dependencies between sub block and aft block
- sub_sub_*: Dependencies within sub block
- *_less: Backward dependency (i-1) - safe for fore/aft, fore/sub,
sub/aft; unsafe for sub/sub due to jamming conflicts
- *_eq: Same iteration dependency (i+0) - safe due to preserved
execution order
- *_more: Forward dependency (i+1) - unsafe due to write-after-write
races between unrolled iterations, except sub/sub case creates conflicts
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedProcessPythonInterface/ScriptedProcessPythonInterface.h')
0 files changed, 0 insertions, 0 deletions