Skip to content

Conversation

sebpop
Copy link
Contributor

@sebpop sebpop commented Sep 3, 2025

Add detailed comments explaining why each function should/shouldn't be unroll-and-jammed based on memory access patterns and dependencies.

Fix loop bounds to ensure array accesses are within array bounds:

  • sub_sub_less: j starts from 1 (not 0) to ensure j-1 >= 0
  • sub_sub_less_3d: k starts from 1 (not 0) to ensure k-1 >= 0
  • sub_sub_outer_scalar: j starts from 1 (not 0) to ensure j-1 >= 0

…ds (NFC)

- Add detailed comments explaining why each function should/shouldn't be
  unroll-and-jammed based on memory access patterns and dependencies.
- Fix loop bounds to ensure array accesses are within array bounds:
  * sub_sub_less: j starts from 1 (not 0) to ensure j-1 >= 0
  * sub_sub_less_3d: k starts from 1 (not 0) to ensure k-1 >= 0
  * sub_sub_outer_scalar: j starts from 1 (not 0) to ensure j-1 >= 0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant