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
It seems that in almost any algorithm, the autoscheduler will generate a bunch of of user warnings like:
Warning:
Outer dim vectorization of var "_0" in function "convolved$10.update(0)"
Warning:
Outer dim vectorization of var "_0" in function "convolved$7.update(0)"
Warning:
Outer dim vectorization of var "_0" in function "convolved$5.update(0)"
Warning:
Outer dim vectorization of var "_0" in function "convolved$3.update(0)"
Warning:
Outer dim vectorization of var "_0" in function "convolved.update(0)"
And also these:
Warning:
Insufficient parallelism for gauss_kernel_normalized
Warning:
Insufficient parallelism for gauss_kernel_normalized$1
Warning:
Insufficient parallelism for gauss_kernel_normalized$10
Warning:
Insufficient parallelism for gauss_kernel_normalized$12
Warning:
Insufficient parallelism for gauss_kernel_normalized$2
Warning:
Insufficient parallelism for gauss_kernel_normalized$3
Warning:
Insufficient parallelism for gauss_kernel_normalized$4
In a Halide-heavy codebase they kind of drown the build log. I don't think they are particularly useful for the user, as there is no way to "generate more parallelism" or steer the autoscheduler to not vectorize outer dimensions. So to me they only look useful for developers working on the autoscheduler, not users of it.
Could they be debug messages instead, at a suitable debug level?
The text was updated successfully, but these errors were encountered:
It seems that in almost any algorithm, the autoscheduler will generate a bunch of of user warnings like:
And also these:
In a Halide-heavy codebase they kind of drown the build log. I don't think they are particularly useful for the user, as there is no way to "generate more parallelism" or steer the autoscheduler to not vectorize outer dimensions. So to me they only look useful for developers working on the autoscheduler, not users of it.
Could they be debug messages instead, at a suitable debug level?
The text was updated successfully, but these errors were encountered: