-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Issues: halide/Halide
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Some ImageParam access can occur in bounds inference on host, but this ignores device_dirty
bug
#8481
opened Nov 19, 2024 by
abadams
[vulkan] Validation errors for DST bit usage on transfer buffers
bug
#8466
opened Nov 6, 2024 by
mcourteaux
Long term performance monitoring using CI
contributor project
enhancement
New user-visible features or improvements to existing features.
#8450
opened Oct 29, 2024 by
abadams
32 minute compile time for max_pool2d_with_indices
autoscheduler
Related to one or more of the Autoschedulers
#8429
opened Sep 28, 2024 by
jansel
Expr constructed with numpy float32 argument gets type halide bool or int32 in Python bindings
bug
release_notes
For changes that may warrant a note in README for official releases.
#8414
opened Sep 9, 2024 by
runenordmo
Determine wheel dependency versions from repo rather than workflow
build
Issues related to building Halide and with CI
#8406
opened Sep 3, 2024 by
alexreinking
Crash and Poor Performance Issues with 3D Stencil Computation using autoscheduler=Adams2019
#8400
opened Aug 27, 2024 by
lsh2233
Device runtime "wrap native" routines should check for invalid device buffers and return an error
#8397
opened Aug 23, 2024 by
slomp
Configure finds Vulkan but target.has_gpu_feature() returns false
#8375
opened Aug 7, 2024 by
yurivict
Halide Auto-Scheduler Produces same Schedules with Different Parallelism Settings
#8356
opened Jul 29, 2024 by
LiQi19970428
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.