Skip to content

Commit 71a9c18

Browse files
authored
add another assumption of at-avx to the README.md
I encountered an issue when using nested loops with multiple loops at the same level. This comment might help other users of this great package when running into such an issue. Did I understand the comment #230 (comment) correctly?
1 parent 0792de3 commit 71a9c18

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ We expect that any time you use the `@avx` macro with a given block of code that
2121
1. Are not indexing an array out of bounds. `@avx` does not perform any bounds checking.
2222
2. Are not iterating over an empty collection. Iterating over an empty loop such as `for i ∈ eachindex(Float64[])` is undefined behavior, and will likely result in the out of bounds memory accesses. Ensure that loops behave correctly.
2323
3. Are not relying on a specific execution order. `@avx` can and will re-order operations and loops inside its scope, so the correctness cannot depend on a particular order. You cannot implement `cumsum` with `@avx`.
24+
4. Are not using multiple loops at the same level in nested loops.
2425

2526
## Usage
2627

0 commit comments

Comments
 (0)