https://github.com/halide/Halide

sort by:
Revision Author Date Message Commit Date
0e2b444 source reorg 11 July 2022, 20:42:01 UTC
36db99d Merge branch 'main' into users/lukas/python-pip 11 July 2022, 18:59:22 UTC
8159dd3 Check RDom::where predicates for race conditions (#6842) Fixes #6808 11 July 2022, 18:39:14 UTC
29ebde9 Better lowering of halving_sub and rounding_halving_add (#6827) * Better lowering of halving_sub and rounding_halving_add Previously, lower_halving_sub and lower_rounding_halving_add both used 9 ops. This change redirects halving_sub to use rounding_halving_add, and redirects rounding_halving_add to use halving_add. In the case that none of these instructions exist natively, this reduces it to 7/8 ops for signed/unsigned halving sub and 6 ops for rounding halving add. More importantly, this lets halving_sub make use of pavgw/b on x86 to reduce it to 3 ops for u8 and u16 inputs. * Make signed rounding_halving_add on x86 use pavgb/w too * Cast result back to signed * Add explanatory comment * Fix comment * Add explanation of signed case 11 July 2022, 18:03:55 UTC
8b60387 Merge branch 'main' into users/lukas/python-pip 10 July 2022, 15:34:40 UTC
23c4cf1 Rearrange subdirectories in python_bindings (#6835) This is intended to facilitate a few things: - Move all Generators used in tests, apps, etc to a single directory to simplify the build rules (this is especially useful for the work in https://github.com/halide/Halide/pull/6764) - Put all the test and apps stuff under a single directory to facilitate adding some Python packaging that can make integration into Bazel/Blaze builds a bit less painful @alexreinking, does this look like the layout we discussed before? 01 July 2022, 17:10:34 UTC
23a1fa8 Disable testing for apps/linear_algebra on x86-32-linux/Make (#6836) * Disable testing for apps/linear_algebra on x86-32-linux/Make This wasn't biting us before because we were disabling *all* apps/ on x86-32-linux (oops); the recent change to remove python testing under Make also re-enabled this test. TL;DR: this can probably be made to work somehow, but it's not worth debugging, since that case is both pretty nice, and already covered under CMake. It's literally not worth the time to fix. * Update Makefile 01 July 2022, 03:48:04 UTC
6838db0 Remove unused function in callable_generator.cpp (#6834) 30 June 2022, 23:11:21 UTC
b2771c1 Scrub Python from Makefile after buildbot update (#6833) 30 June 2022, 21:26:13 UTC
fac313e Add a new, alternate JIT-call convention (#6777) * Prototype of revised JIT-call convention Experiment to try out a way to call JIT code in C++ using the same calling conventions as AOT code. Very much experimental. * Update Pipeline.h * Add Python support for `compile_to_callable` + make empty_ucon static * Update PyCallable.cpp * Update buffer.py * wip * Update callable.py * WIP * Update custom_allocator.cpp * Update Callable.cpp * Add Generator support for Callables * Update Generator.cpp * Update PyPipeline.cpp * Fixes * Update callable.cpp * Update CMakeLists.txt * create_callable_from_generator * More cleanup * Update Generator.cpp * Fix Python bounds inference * Add Python wrapper for create_callable_from_generator() + Add kwarg support for Callable * Add set_generatorparam_values() + usage * Fix auto_schedule/machine_params parsing The recent refactoring that added `execute_generator` accidentally nuked setting these two GeneratorParams. Oops. Fixed. * Move the type-checking code into a constexpr code * Update Callable.h * clang-tidy * CLANG-TIDY * Add `make_std_function`, + more general cleanup * Update example_jittest.cpp * Update Callable.h * Update Callable.h * More tweaking, smaller CallCheckInfo * Still more cleanup * make_std_function now does Buffer type/dim checking where possible * Add tests for calling `AbstractGenreator::compile_to_callable()` directly * enable exports * Various fixes * Improve fill_slot for Halide::Buffer * kill report_if_error * Update callable_bad_arguments.cpp * Update Pipeline.cpp * Revise error handling * Update Callable.cpp * Update callable.py * Update callable_generator.cpp * Update callable.py * HALIDE_MUST_USE_RESULT -> HALIDE_FUNCTION_ATTRS for Callable 30 June 2022, 20:18:42 UTC
17382ee Merge branch 'main' into users/lukas/python-pip 30 June 2022, 18:42:16 UTC
60d2b98 Remove Python bindings from Makefiles (#6821) * Remove Python bindings from Makefiles * Restore test_li2018 in Makefile (now C++-only) * Add dummy `test_python` target for buildbots 30 June 2022, 18:23:48 UTC
ece5fb7 Apply CMAKE_C_COMPILER_LAUNCHER to initmod clang calls (#6831) 30 June 2022, 15:55:12 UTC
d36cd04 Change stub module names in Python to be _pystub rather than _stub (#6830) This is a bit finicky, but making this the default nomenclature will make some downstream usages less ambiguous and a bit easier to manage. (Yes, I realize that #6821 removes the Makefile entirely, but until it lands, it needs fixing there too.) 29 June 2022, 23:15:07 UTC
7e31535 Move more packaging logic into python_bindings 29 June 2022, 04:10:26 UTC
02659eb Make CMake install the same layout as setuptools 29 June 2022, 03:36:20 UTC
b360124 Re-enable Python bindings in main build 29 June 2022, 02:24:58 UTC
985515a Ignore MANIFEST.in 29 June 2022, 02:24:34 UTC
cc04fdb Suppress spurious unused variable warnings 29 June 2022, 02:06:15 UTC
ffb77ea De-duplicate libHalide.so.15.0.0 and SONAME link in wheel 29 June 2022, 02:01:43 UTC
b3956cc Detect Halide version in setup.py 29 June 2022, 01:58:09 UTC
7c1dbb0 Remove version.py 29 June 2022, 00:52:34 UTC
2f55c5a Set python bindings' RPATH to $ORIGIN 29 June 2022, 00:47:20 UTC
036b4f3 Install imported libHalide.so with Python bindings 29 June 2022, 00:46:36 UTC
92a1497 Trim trailing whitespace 28 June 2022, 23:56:06 UTC
5a492d1 Restore robust target names and install rules 28 June 2022, 23:53:09 UTC
cb59dbd Check that exceptions are RTTI are enabled 28 June 2022, 23:52:34 UTC
8074e24 Add gitignore rules for Python builds 28 June 2022, 23:51:55 UTC
76fa110 Add PyPI preset 28 June 2022, 23:25:44 UTC
3e142cf Tweak python apps for better Blaze/Bazel compatibility (#6823) * Tweak python apps/tutorials for better Blaze/Bazel compatibility - Don't write to current directory (rely on an env var to say where to write) - Don't read from arbitrary absolute paths (again, rely on an env var) - Drive-by removal of unnecessary #include in Codegen_LLVM.cpp inside a lambda (!) * Recommended fixes * Revert all changes to tutorial * Revise apps * Remove apps_helpers.py 28 June 2022, 20:55:16 UTC
508dd36 Restore trailing newline 28 June 2022, 17:25:18 UTC
4c27754 Format setup.py 28 June 2022, 17:23:41 UTC
6f530dc Make setup.py inject pybind11 paths 28 June 2022, 17:22:47 UTC
e2f3c81 Correct dependencies 28 June 2022, 17:22:15 UTC
fd46aa5 Spoof find_package(Halide) for internal builds 28 June 2022, 17:20:58 UTC
f7fb197 Merge branch 'main' into users/lukas/python-pip 28 June 2022, 16:55:53 UTC
c12f8a5 Fix for top-of-tree LLVM (#6825) 28 June 2022, 16:52:25 UTC
e0a9825 Update presets to format version 3 (#6824) 28 June 2022, 15:46:06 UTC
feba77c Rework .gitignore (#6822) * reorganize .gitignore * Add exclusions for CMake build * .gitignore: comment, drop stale rules * fully and precisely exclude CMake build tree * add debugging directions to .gitignore * ignore CMake install tree * Sort groups 28 June 2022, 15:39:48 UTC
9e5c5ce Add support for vscale vector code generation. (#6802) Add support for vscale vector code generation. Factored from the fixed_length_vectors branch to make PRs smaller and easier to review. This will be used to support the ARM SVE/SVE2 and RISC V Vector architectures. 27 June 2022, 23:08:12 UTC
0e17e67 [CMake] Mark multi-threaded tests as such (#6810) 27 June 2022, 18:48:05 UTC
77c8f38 Scikit build for python bindings 24 June 2022, 16:30:24 UTC
fc0f1f7 Fix two minor bugs triggered by an or reduction with early-out (#6807) * Fix two minor bugs triggered by a or reduction with early-out * Gotta print success * Appease clang-tidy 14 June 2022, 22:05:08 UTC
ce75862 Rewrite strided loads of 4 in AlignLoads (#6806) * Rewrite strided loads of 4 in AlignLoads * Add a check for strided 4 load 14 June 2022, 18:08:36 UTC
0ec2740 Fix auto_schedule/machine_params parsing (#6804) The recent refactoring that added `execute_generator` accidentally nuked setting these two GeneratorParams. Oops. Fixed. 06 June 2022, 21:07:18 UTC
f712f4f Minor typedef cleanup (#6800) * cleanup * format 06 June 2022, 16:42:30 UTC
8b31327 Make all tests default to `-fvisibility=hidden` (#6799) * Step 1 * still more * Export the error classes so they can be caught 02 June 2022, 16:44:26 UTC
00b5728 Silence a "possibly uninitialized" warning (#6797) * Silence a "possibly uninitialized" warning At least one compiler thinks we can use this without initialization, which isn't true, but this silences it. * trigger buildbots 02 June 2022, 16:43:40 UTC
e832c4f Pacify clang-tidy (#6796) * Pacify clang-tidy Newer versions can warn about "parameter 'f' shadows member inherited from type 'StubOutputBufferBase'", etc -- easy enough * Update .clang-tidy 01 June 2022, 21:13:24 UTC
4f2251c Add missing include to test_sharding.h (#6795) 01 June 2022, 19:46:03 UTC
2b29bde slow tests should support sharding (#6780) * slow tests should support sharding The simd_op_check test suite is pretty slow (especially for wasm, where it is interpreted); at one point we tried to use ThreadPool to speed it up, but too many pieces of Halide IR aren't threadsafe and we disabled it long ago. This removes the ThreadPool usage entirely, and instead adds support for the GoogleTest 'sharded test' protocol, which uses certain env vars to allow a test to opt in for splitting its test into smaller pieces. At present our buildbot isn't attempting to make use of this feature, but it will be a big win for downstream usage in Google, where tests that run "too long" are problematic and splitting them into multiple shards makes various day to day activiites much more pleasant. 01 June 2022, 19:07:23 UTC
76793b4 Add Target support for architectures with implementation specific vector size. (#6786) Move vector_bits_* Target support from fixed_width_vectors branch to make smaller PRs. 31 May 2022, 23:37:08 UTC
255ff18 hexagon_scatter test should run only if target has HVX (#6793) It will run otherwise, but is slow on some other targets; rather than trying to (e.g.) shard it, just skip it 31 May 2022, 21:32:40 UTC
74d9909 Define an AbstractGenerator interface (#6637) * AbstractGenerator (rebased, v3) * Update AbstractGenerator.h * clang-format * Update Generator.cpp * IOKind -> ArgInfoKind * Various cleanups of AbstractGenerator * clang-format * fix pystub * Update abstractgeneratortest_generator.cpp * dead code * ArgInfoDirection * cleanup * Delete PyGenerator.cpp * Update PyStubImpl.cpp * Update PyStubImpl.cpp * Fixes from review comments * Remove `get_` prefix from getters in AbstractGenerator * Missed some fixes * Fixes * Add GeneratorFactoryProvider for generate_filter_main() * Add GeneratorFactoryProvider to generate_filter_main() This provides hooks to allow overriding the Generator(s) that generate_filter_main() can use; normally it defaults to the global registry of C++ Generators, but this allows for (e.g.) alternate-language-bindings to selectively override this (e.g. to enumerate only Generators that are visible in that language, etc). (No visible change in behavior from this PR; this is just cherry-picked from work-in-progress elsewhere to simplify review & merge) * Update Generator.cpp * fixes * Update Generator.cpp * Restore build_module() and build_gradient_module() methods * Update Generator.h * fixes * Update Generator.cpp * Update AbstractGenerator.h 31 May 2022, 18:29:23 UTC
25f615d halide_type_of<>() should always be constexpr (#6790) The ones in HalideRuntime.h have been marked constexpr for a while, but the ones in Float16.h got missed 31 May 2022, 17:15:41 UTC
3ba2f94 LLVM codegen: register AA pipeline if LLVM is older than 14 (#6785) It's the default after https://reviews.llvm.org/D113210 / https://github.com/llvm/llvm-project/commit/13317286f8298eb3bafa9ddebd1c03bef4918948, but still needs to be done for earlier LLVM's. Refs. https://github.com/halide/Halide/issues/6783 Refs. https://github.com/halide/Halide/pull/6718 Partially reverts https://github.com/halide/Halide/pull/6718 27 May 2022, 19:35:32 UTC
0f7d548 Move some options from execute_generator back to generate_filter_main (#6787) Loading plugins and setting the default autoscheduler name both change global state, which isn't a desirable fit for execute_generator(), since it's not intended to mutate global state. (Mutating the state from a main() function is of course a reasonable thing to do.) 27 May 2022, 17:18:23 UTC
d0c53fa [miscompile] Don't de-negate and change direction of shifts-by-unsigned (#6782) I'm afraid the problem is really obvious: https://github.com/halide/Halide/blob/b5f024fa83b6f1cfe5e83a459c9378b7c5bf096d/src/CodeGen_LLVM.cpp#L2628-L2649 ^ the shift direction is treated as flippable by the codegen iff the shift amount is signed :) The newly-added test fails without the fix. I've hit this when writing tests for https://github.com/halide/Halide/pull/6775 26 May 2022, 17:33:31 UTC
ad1e7f6 Convert some assert-only usage of output_types() -> types() (#6779) 24 May 2022, 18:31:02 UTC
83a90e7 Allow overriding of `Generator::init_from_context()` for debug purposes (#6760) * Allow overriding of `Generator::init_from_context()` for debug purposes * Update Generator.h * Attempt to clarify contract 23 May 2022, 18:31:19 UTC
d973993 Add execute_generator() API (#6771) This refactors the existing `generate_filter_main()` call in two, moving the interesting implementation of how to drive AOT into the new `execute_generator()` call (reducing `generate_filter_main()` to parsing argc/argv and error reporting). The new `execute_generator()` is intended to be used (eventually) from Python, as a way to drive Generator compilation from a Python script more easily. The PR doesn't provide a Python wrapper for this call yet (that will come in a subsequent PR). Also, a drive-by removal of the "error_output" arg to generate_filter_main() -- AFAICT, no one has ever used it for anything but stderr, and the refactoring now just directs all errors to `user_error` uniformly. 23 May 2022, 18:31:03 UTC
56acc6e Fix annoying typo in Func.h (#6774) Update Func.h 19 May 2022, 21:22:46 UTC
b5f024f Fix fundamental confusion about target/tune CPU (#6765) * Fix fundamental confusion about target/tune CPU Sooo. Uh, remember when in https://github.com/halide/Halide/pull/6655 we've agreed that we want to add support to precisely specify the CPU for which the code should be *tuned* for, but not *targeted* for. Aka, similar to clang's `-mtune=` option, that does not affect the ISA set selection? So guess what, that's not what we did, apparently. `CodeGen_LLVM::mcpu()` / `halide_mcpu` actually do specify the *target* CPU. It was obvious in retrospect, because e.g. `CodeGen_X86::mattrs()` does not, in fact, ever specify `+avx2`, yet we get AVX2 :) So we've unintentionally added `-march=` support. Oops. While i'd like to add `-march=` support, that was not the goal here. Fixing this is complicated by the fact that `llvm::Target::createTargetMachine()` only takes `CPU Target` string, you can't specify `CPU Tune`. But this is actually a blessing in disguise, because it allows us to fix another bug at the same time: There is a problem with halide "compile to llvm ir assembly", a lot of information from Halide Target is not //really// lowered into LLVM Module, but is embedded as a metadata, that is then extracted by halide `make_target_machine()`. While that is not a problem in itself, it makes it *impossible* to dump the LLVM IR, and manually play with it, because e.g. the CPU [Target] and Attributes (ISA set) are not actually lowered into the form LLVM understands, but are in some halide-specific metadata. So, to fix the first bug, we must lower the CPU Tune into per-function `"tune-cpu"` metadata, and while there we might as well lower `"target-cpu"` and `"target-features"` similarly. * Address review notes * Hopefully silence bogus issue reported by ancient GCC * Call `set_function_attributes_from_halide_target_options()` when JIT compiling * Fix grammar 19 May 2022, 17:10:53 UTC
61f6af7 Add Func::type()/types(), deprecate Func::output_type()/output_types() (#6772) * rename GIOBase::type() and friends * Func::output_type() -> Func::type() * Add type() forwarders for inputs * Add Func::dimensions() wrapper * Update Func.h 19 May 2022, 16:20:19 UTC
13a5470 Update the list of fused_pairs and run validate_fused_group for specalization definitions too (#6770) * Update the list of fused_pairs and run validate_fused_group for specialization definitions too. Fixes https://github.com/halide/Halide/issues/6763. * Address review comments * Add const to auto& 18 May 2022, 17:30:04 UTC
25a3272 add_python_aot_extension should use FUNCTION_NAME for the .so output … (#6767) add_python_aot_extension should use FUNCTION_NAME for the .so output (otherwise you can't produce multiple aot extensions from the same Generator) 16 May 2022, 17:46:56 UTC
cc41e65 Fix Param<T>::set_estimate for T=void (#6766) * Fix Param<T>::set_estimate for T=void * Add tests 16 May 2022, 17:29:13 UTC
09a986e Expand the x86 SIMD variants tested in correctness_vector_reductions (#6762) A recent bug in LLVM codegen was missed because it only affected x86 architectures with earlier-than-AVX2 SIMD enabled; it didn't show up for AVX2 or later. This revamps correctness_vector_reductions to re-run multiple times when multiple SIMD architectures are available on x86 systems. (correctness_vector_reductions was chosen here because it reliably demonstrated the specific failures in this case.) 13 May 2022, 20:56:47 UTC
4ab4ad9 Minor metadata-related cleanups (#6759) (Harvested from #6757, which probably won't land) - Add clarifying comment/reference in Generator - Add assertion to compile_to_multitarget() function - Fix misleading/wrong code in correctness_compile_to_multitarget 13 May 2022, 01:31:38 UTC
b38b661 Deprecate disable_llvm_loop_opt (#4113) (#6754) This PR proposes to (finally) deprecate disable_llvm_loop_opt: - make LLVM codegen default to no loop optimization; you must use enable_llvm_loop_opt explicitly to enable it - disable_llvm_loop_opt still exists, but does nothing (except issue a user_warning that the feature is deprecated) - Remove various uses of disable_llvm_loop_opt - Add comments everywhere that the default is different in Halide 15 and that the disable_llvm_loop_opt feature will be removed entirely in Halide 16 Note that all Halide code at Google has defaulted to having disable_llvm_loop_opt set for ~years now, so this is a well-tested codepath, and consensus on the Issue seemed to be that this was a good move. 10 May 2022, 20:58:26 UTC
a2e89d8 Add GeneratorFactoryProvider to generate_filter_main() (#6755) * Add GeneratorFactoryProvider to generate_filter_main() This provides hooks to allow overriding the Generator(s) that generate_filter_main() can use; normally it defaults to the global registry of C++ Generators, but this allows for (e.g.) alternate-language-bindings to selectively override this (e.g. to enumerate only Generators that are visible in that language, etc). (No visible change in behavior from this PR; this is just cherry-picked from work-in-progress elsewhere to simplify review & merge) * Update Generator.cpp * Fix error handling 10 May 2022, 01:07:57 UTC
a986078 Deprecate GeneratorContext getters with `get_` prefix (#6753) Minor hygiene: most getters in Halide don't have a `get_` prefix. These are very rarely used (only one instance in our test suite I could find) but, hey, cleanliness. 09 May 2022, 21:38:41 UTC
47d8103 Add a `HalideError` base class to Python bindings (#6750) * Add a `HalideError` base class to Python bindings Per suggestion from @alexreinking, this remaps all exceptions thrown by the Halide Python bindings to be `halide.HalideError` (or a subclass thereof), rather than plain old `RuntimeError`. * Remove scalpel left in patient * Don't use a subclass for PyStub error handling 06 May 2022, 00:49:40 UTC
6fbf203 Update hannk README link to hosted models page (#6749) The current one is being sunsetted 05 May 2022, 16:06:37 UTC
557690e Update WABT to 1.0.29 (#6748) 05 May 2022, 16:06:21 UTC
c8531a5 Silence "may be used uninitialized" in Buffer::for_each_element() (#6747) In at least one version of GCC (Debian 11.2.0-16+build1), an optimized build using `Buffer::for_each_element(int *pos)` will give (incorrect) compiler warnings/errors that "pos may be used uninitialized). From inspection of the code I feel pretty sure this is a false positive -- i.e., the optimizer is confused -- and since no other compiler we've encountered issues a similar warning (nor do we see actual misbehavior), I'm inclined not to worry -- but the warning does break some build configurations. Rather than try to fight with selectively disabling this warning, I'm going to propose inserting a memset() here to reassure the compiler that the memory really is initialized; while it's unnnecessary, it's likely to be insignificant compared to the cost of usual calls to for_each_element(). (BTW, this is not a new issue, I've seen it for quite a while as this GCC is the default on one of my Linux machines... it just finally annoyed me enough to want to make it shut up.) 05 May 2022, 01:17:40 UTC
1606039 Revise PyStub calling convention for GeneratorParams (#6742) This is a rethink of https://github.com/halide/Halide/pull/6661, trying to make it saner in anticipation of the ongoing Python Generator work. TL;DR: instead of mixing GeneratorParams in with the rest of the keywords, segregate them into an optional `generator_params` keyword argument, which is a plain Python dict. This neatly solves a couple of problems: - synthetic params with funky names aren't a problem anymore. - error reporting is simpler because before an unknown keyword could have been intended to be a GP or an Input. - GP values are now clear and distinct from Inputs, which is IMHO a good thing. This is technically a breaking change, but I doubt anyone will notice; this is mainly here to get a sane convention in place for use with Python Generators as well. Also, a drive-by change to Func::output_types() to fix the assertion error message. 04 May 2022, 00:16:26 UTC
92dfb61 Add __pycache__ to toplevel .gitignore file (#6743) 02 May 2022, 18:14:18 UTC
f376cbb Silence "unscheduled update stage" warnings in msan_generator.cpp (#6740) 30 April 2022, 17:20:46 UTC
e6260a8 Add forwarding for the recently-added Func::output_type() method (#6741) 30 April 2022, 17:20:22 UTC
41b2d07 Fix regression from #6734 (#6739) That change inadvertently required the RHS of an update stage that used `+=` (or similar operators) to match the LHS type, which should be required (implicit casting of the RHS is expected). Restructured to remove this, but still ensure that auto-injection of a pure definition matches the required types (if any), and updated tests. 28 April 2022, 20:53:19 UTC
fc0f4ed Add missing #include <functional> in ThreadPool.h (#6738) * Add missing #include <function> in ThreadPool.h * Update ThreadPool.h 28 April 2022, 18:31:38 UTC
00f4b29 More typed-Func work (#6735) - Allow Func output_type(s)(), outputs(), dimensions(), and output_buffer(s)() to be called on undefined Funcs if the Func has required_type and required_dimensions specified. This allows for greater flexibility in defining pipelines in which you may want to set or examine constraints on a Func that hasn't been defined yet; previously this required restructuring code or other awkwardness. - Ensure that the Funcs that are defined for ImageParams and Generator fields define the types-and-dims when known. - Add some tests. 28 April 2022, 01:33:49 UTC
799c546 Augment Halide::Func to allow for constraining Type and Dimensionality (#6734) This enhances Func by allowing you to (optionally) constrain the type(s) of Exprs that the Func can contain, and/or the dimensionality of the Func. (Attempting to violate either of these will assert-fail.) There are a few goals here: - Enhanced code readability; in cases where a Func's values may not be obvious from the code flow, this can allow an in-code way of declaring it (rather than via comments) - Enhanced type enforcement; specifying constraints allows us to fail in type-mismatched compilations somewhat sooner, with somewhat better error messages. - Better symmetry for AOT/JIT code generation with ImageParam, in which the inputs (ImageParam) have a way to specify the required concrete type, but the outputs (Funcs) don't. If this is accepted, then subsequent changes will likely add uses where it makes sense (e.g., the Func associated with an ImageParam should always have both type and dimensionality specified since it will always be well-known). Note that this doesn't add any C++ template class for static declarations (e.g. `FuncT<float, 2>` -> `Func(Float(32), 2)`); these could be added later if desired. 27 April 2022, 20:48:27 UTC
86a4a59 Remove `rounding_halving_sub` and non-existent arm rhsub instructions (#6723) * remove arm (s | u)rhsub instructions * remove rounding_halving_sub intrinsic entirely 26 April 2022, 19:14:34 UTC
f5c77ce Deprecate variadic-template version of Realization ctor (#6695) * Deprecate variadic-template version of Realization ctor The variadic-template approach was useful before C++11 (!) added brace initialization, but preferring an explicit vector-of-Buffer is arguably better, and provides better symmetry with the Python bindings. Also, some drive-by tweaks to other Realization methods. * Update PyPipeline.cpp * trigger buildbots 25 April 2022, 17:00:10 UTC
85b9f29 Grab-bag of minor Python fixes (#6725) 21 April 2022, 20:02:00 UTC
754018b Add Func::output_type() method (#6724) * Add Func::output_type() method * Add Python 21 April 2022, 19:58:49 UTC
aa384af `get_amd_processor()`: implement detection for the rest of supported AMD CPU's (#6711) I have *not* personally tested that these are detected correctly, Cross-reference between * https://github.com/llvm/llvm-project/blob/955cff803e081640e149fed0742f57ae1b84db7d/llvm/lib/Support/Host.cpp#L968-L1041 * https://github.com/llvm/llvm-project/blob/955cff803e081640e149fed0742f57ae1b84db7d/compiler-rt/lib/builtins/cpu_model.c#L520-L586 * https://github.com/gcc-mirror/gcc/blob/000c1b89d259fadb466e1f2e63c79da45fd17372/gcc/common/config/i386/cpuinfo.h#L111-L264 21 April 2022, 16:32:56 UTC
accc644 Remove legacy::FunctionPassManager usage in Codegen_PTX_Dev (#6722) LLVM devs indicate that none of the passes in this usage actually do anything and it can be safely removed. 21 April 2022, 03:01:15 UTC
3b3e89e Smarten type_of<> for fn ptrs; fix async_parallel for C backend (#6719) * Smarten type_of<> for fn ptrs; fix async_parallel for C backend (Fixes #2093) This basically just adds the right type annotations to make the parallel code produced by the C backend compile properly. This could have been fixed by inserted some brute-force void* casting into the C backend, but this felt a lot cleaner. The one thing here I'm a little unsure about is how I extended the Type code to be able to handle function-pointer types correctly; it works but doesn't feel very elegant. * Update Makefile * Update LowerParallelTasks.cpp * FunctionTypedef 20 April 2022, 17:01:39 UTC
a07d3e4 Closure functions for parallel tasks should be internal, not external (#6720) Minor optimization. 20 April 2022, 16:50:30 UTC
460c77e Update CodeGen_PTX_Dev to use new PassManager (#6718) * Update CodeGen_PTX_Dev to use new PassManager This was still using the LegacyPassManager for optimization, which will be going away at some point. (Code changes by @alinas; I'm just opening this PR on her behalf) * Fixes after review 20 April 2022, 00:25:35 UTC
65ba16e Combine string constants in combine_strings() (#6717) * Combine string constants in combine_strings() This is a pretty trivial optimization, but when printing (or enabling `debug`), it cuts the number of `halide_string_to_string()` calls we generate by ~half. * Update IROperator.cpp 19 April 2022, 21:53:00 UTC
01ca823 ARM vst mangling needs to be conditional on opaque ptrs (#6716) The fixes from last week regarding mangling of arm vst intrinsics needs to be made conditional on whether the pointer is opaque or not; this will change based on whether `-D CLANG_ENABLE_OPAQUE_POINTERS=ON|OFF` is defined when LLVM is built, but should be sniffed via this API, according to my LLVM contact. 19 April 2022, 20:04:15 UTC
4df3c5d Remove the last remaining call to getPointerElementType() (#6715) * Remove the last remaining call to getPointerElementType() LLVM is moving to opaque pointers, we must have missed this one in previous work * ARM vst mangling needs to be conditional on opaque ptrs The fixes from last week regarding mangling of arm vst intrinsics needs to be made conditional on whether the pointer is opaque or not; this will change based on whether `-D CLANG_ENABLE_OPAQUE_POINTERS=ON|OFF` is defined when LLVM is built, but should be sniffed via this API, according to my LLVM contact. * Revert "ARM vst mangling needs to be conditional on opaque ptrs" This reverts commit 9901314ff75dd0bf651b23d09c1d1f5f07d49ffd. 19 April 2022, 19:54:12 UTC
60a909f Fix type-mangling for vst on arm32 for LLVM15 (#6705) 14 April 2022, 16:49:38 UTC
77f7f5e Python: make Func implicitly convertible to Stage (#6702) (#6704) This allows for `compute_with` and `rfactor` to work more seamlessly in Python. Also: - Move two compute_with() variant bindings from PyFunc and PyStage to PyScheduleMethods, as they are identical between the two - drive-by removal of redundant `py::implicitly_convertible<ImageParam, Func>();` call 13 April 2022, 21:31:17 UTC
87c0cc9 llvm no longer wants a type suffix on vst intrinsics (#6701) * llvm no longer wants a type suffix on vst intrinsics * Fix silly mistake * Change 64-bit only Co-authored-by: Andrew Adams <anadams@adobe.com> 12 April 2022, 23:38:56 UTC
3d7b977 Drop support for Matlab extensions (#6696) * Drop support for Matlab extensions Anecdotally, this hasn't been used in ~years, and the original author (@dsharletg) had suggested dropping it a while back. I'm going to propose we go ahead and drop it for Halide 15 and see who complains. * Fixes for top-of-tree LLVM * Update force_include_types.cpp * trigger buildbots * Update CodeGen_LLVM.cpp 12 April 2022, 23:33:02 UTC
back to top