-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Begin refactor for 1-11 * Tidy up a bit * Tidy up a bit further * Some work * StandardFDataType includes NoFData * Basic tests passing for Memory * Some work * Initial memory implementation + array tests * Check number of arguments returned by rrule * More imports * Alterations to abstract interpreter for 1.11 * Ignore versioned manifests * Qualify import * Add lgetfield and order for getfield to utils * Handle all lgetfield and getfield cases with memory, memoryref, and array * Updates for 1.11 * Run CI on 1.11 * Improve utils for UnionAlls * Do not inline away debug information * Tidy up utilities * Test utilities * Update tangent functionality * Fix some codual-related problems * Fix edge case in memoryrefset * Handle weird PiNode * Test that PiNode edge case runs * Remove commented-out code * Remove redundant semicolon * Remove commented-out code * Move lsetfield definition to utils * Improve remove_unreachable_blocks * Uncomment a various array integration tests * Add lsetfield to custom tangent type testing * Rename remove_unreachable_block uses for mutating version * Skip diff_test with compiler problems * Move rules around to support both 1.11 and 1.10 * Add rule for sincos * Run more tests on tasks * Attempt to avoid allocations * Disable Enzyme in benchmarking on 1.11 * Avoid having to define setfield and lsetfield rules * Do not test tasks more stringently * Fix task tests * Restrict LuxLib versions * Fix increment and tuple_map for NamedTuple and testing * generalise lsetfield * Protect more things for the GC * Fix typo * Revert changes to codual types * Tidy up coduals * Fix on 1.10 * Sort out 1.10 and 1 * Sort out CI names * Fix up 1.10 testing * Restrict runners * Formatting * Bump patch
- Loading branch information
1 parent
c9b569c
commit 997398c
Showing
42 changed files
with
2,752 additions
and
1,559 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
/Manifest.toml | ||
/Manifest-v1.11.toml | ||
dev | ||
bench/Manifest.toml | ||
analysis_results | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
module MooncakeAllocCheckExt | ||
|
||
using AllocCheck, Mooncake | ||
import Mooncake.TestUtils: check_allocs, Shim | ||
|
||
@check_allocs check_allocs(::Shim, f::F, x::Tuple{Vararg{Any, N}}) where {F, N} = f(x...) | ||
|
||
end |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
997398c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JuliaRegistrator register
997398c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Registration pull request updated: JuliaRegistries/General/117349
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via: