You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ We expect that any time you use the `@avx` macro with a given block of code that
21
21
1. Are not indexing an array out of bounds. `@avx` does not perform any bounds checking.
22
22
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.
23
23
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.
0 commit comments