d5aa598 | KristofferC | 30 September 2022, 13:54:57 UTC | change Pkg to weak deps supported version | 30 September 2022, 13:54:57 UTC |
5f3e102 | KristofferC | 30 September 2022, 13:54:10 UTC | add support for weak dependencies in code loading and precompilation | 30 September 2022, 13:54:10 UTC |
4db5ffa | Lilith Orion Hafner | 30 September 2022, 12:20:03 UTC | sort du.defs (#46877) | 30 September 2022, 12:20:03 UTC |
f98b1ea | Shuhei Kadowaki | 30 September 2022, 11:24:48 UTC | Merge pull request #46971 from JuliaLang/avi/modifyfieldinfo - compiler: setup `ModifyFieldInfo` callinfo - atomics: add simple test cases for `modifyfield!` inlining | 30 September 2022, 11:24:48 UTC |
90dbc5d | Keno Fischer | 30 September 2022, 08:37:29 UTC | Don't rely on implicit information for statement used-ness. (#46966) Currently, we were relying on the implicitly passed in sv.currpc to determine whether a call result type was needed or not. This is usually correct, but not always. For example, in apply_iterate, we actually end up calling various `iterate` methods and inspect their result, so the used-ness of the outer apply_iterate is irrelevant. Similar examples occur in external packages. Fix this issue by refactoring the code to thread through an extra `StmtInfo` object that record used-ness (and potentially other stmt attributes in the future). | 30 September 2022, 08:37:29 UTC |
08aa8e7 | Tim Besard | 30 September 2022, 07:45:38 UTC | IRCode display: consider new nodes when determining max SSA id. (#46969) | 30 September 2022, 07:45:38 UTC |
848adcf | Tim Besard | 30 September 2022, 07:43:34 UTC | IncrementalCompact: trim undef nodes introduced by copy propagation. (#46968) | 30 September 2022, 07:43:34 UTC |
ccde9fa | Udoh Jeremiah | 30 September 2022, 05:50:58 UTC | doc: add example and wiki link to issubnormal docstring (#46899) | 30 September 2022, 05:50:58 UTC |
142bb6c | Shuhei Kadowaki | 30 September 2022, 05:00:32 UTC | atomics: add simple test cases for `modifyfield!` inlining | 30 September 2022, 05:00:32 UTC |
6c75aab | Shuhei Kadowaki | 29 September 2022, 12:24:35 UTC | compiler: setup `ModifyFieldInfo` callinfo This makes it more explicit that `modifyfield!` call is special-cased. It would be more aligned with the other specially-handled builtins like `invoke` and `Core.finalizer`. | 30 September 2022, 04:31:23 UTC |
6e1e6fa | Glen Hertz | 29 September 2022, 19:13:05 UTC | Add `filter(func)` method (#41173) Add `filter(func)` method | 29 September 2022, 19:13:05 UTC |
f346735 | Jameson Nash | 29 September 2022, 18:52:37 UTC | avoid timing race in async test (#46941) This is the test from #27164. The test was checking whether sleep(1) (which is started first) or sleep(0.05) (which is nominally shorter) returned first. Use an Event instead so that they are explicitly ordered. Fixes #46360 | 29 September 2022, 18:52:37 UTC |
6863249 | Elliot Saba | 29 September 2022, 16:20:59 UTC | [LBT] Bump to v5.2.0 (#46960) This should fix issues on i686 linux and using Accelerate on aarch64 darwin. LBT itself is now much more thoroughly tested [0]. [0] https://buildkite.com/julialang/libblastrampoline | 29 September 2022, 16:20:59 UTC |
9fd4087 | Daniel Karrasch | 29 September 2022, 08:30:58 UTC | Generalize 2-arg `eigen` towards `AbstractMatrix` (#46797) | 29 September 2022, 08:30:58 UTC |
9118373 | Jameson Nash | 29 September 2022, 07:02:14 UTC | [FileWatching] improve lock_times test (#46942) Make this test slightly stricter to pass, to try to investigate #45982 better. | 29 September 2022, 07:02:14 UTC |
4b042c8 | Jameson Nash | 29 September 2022, 07:00:45 UTC | gf: detect more ambiguities (#46922) As long as we find at least one other method that conflicts fully, we know they will exist together for all subtypes, and always be ambiguous for all subtypes too. This is already the algorithm used by method insertion to decide if the new method is ambiguous with a "missing" method. Fix #46601 | 29 September 2022, 07:00:45 UTC |
5588623 | Jameson Nash | 29 September 2022, 06:53:32 UTC | remove bad test from get_updated_dict (#46944) PR #42328 (21ebabf7904061b4283b4428efa8fa4d6e8d0bc6) already fixed issue #35217 by removing the bad test. Now also remove the nonsensical comment condition from loading.jl. | 29 September 2022, 06:53:32 UTC |
170d643 | Jameson Nash | 29 September 2022, 06:51:37 UTC | codegen: fix compute_va_type issue with Type (#46953) Issue noted in #42498. This should be the same as Core.Compiler.tuple_tfunc. Otherwise we might accidentally constant-fold something like: code_llvm((x...) -> x isa Tuple{Type{Tuple{Any}},Int}, (Type{Tuple{Any}}, Int)) to return true. This is rarely a compile-sig in practice, so it does not usually affect code, but is observable there in the IR. | 29 September 2022, 06:51:37 UTC |
8e44510 | Udoh Jeremiah | 29 September 2022, 06:44:54 UTC | doc: add return type for ^ operator for strings (#46884) | 29 September 2022, 06:44:54 UTC |
7364207 | Udoh Jeremiah | 29 September 2022, 06:43:31 UTC | function signature for the "^" operator for regex (#46885) | 29 September 2022, 06:43:31 UTC |
ebaf4c8 | Udoh Jeremiah | 29 September 2022, 06:42:46 UTC | doc: update example on % for integers (#46893) | 29 September 2022, 06:42:46 UTC |
594fcd8 | Udoh Jeremiah | 29 September 2022, 06:39:29 UTC | doc: ndigits relationship with zero (#46900) | 29 September 2022, 06:39:29 UTC |
c548bd3 | Shuhei Kadowaki | 29 September 2022, 06:33:28 UTC | irinterp: clean up IR abstract interpretation subroutines [NFC] (#46917) * clean up `reprocess_instruction!` * setup `IRInterpretationState` for irinterp state management | 29 September 2022, 06:33:28 UTC |
75e96c5 | Erik Schnetter | 29 September 2022, 01:41:57 UTC | Correct typographical error in comment (#46959) | 29 September 2022, 01:41:57 UTC |
e7a5c36 | Tim Besard | 28 September 2022, 15:01:17 UTC | reland "Fix serialization of code instances" (#46939) If they are encountered in a Julia object directly, as opposed to e.g. during serialization of a method instance, we'll have first populated the backref table as part of jl_serialize_value, so we need to skip that check during code instance serialization. | 28 September 2022, 15:01:17 UTC |
b2c2abf | Jameson Nash | 28 September 2022, 14:18:20 UTC | Revert "Inlining: Remove outdated code path for GlobalRef movement (#46880)" (#46951) This reverts commit cda61ef68f49cab66f45b731b7cffbb79a1d3c90. This seems to be exposing (or less likely actually causing) some problems with GC rooting, dead-code elimination, and/or valid IR: #46940 and #46943 | 28 September 2022, 14:18:20 UTC |
3e0cd2c | Tim Besard | 28 September 2022, 14:17:48 UTC | IncrementalCompact: always show the separator. (#46946) There was an off-by-one error, but always showing the separator is even clearer, and consistent with how it's shown at the top when nothing has been compacted yet. | 28 September 2022, 14:17:48 UTC |
1afa368 | Dilum Aluthge | 28 September 2022, 06:36:02 UTC | Revert "Fix serialization of code instances. (#46373)" (#46936) This reverts commit ff4f86dce6660f717b2978ef9d9123f1ec3393ea. | 28 September 2022, 06:36:02 UTC |
d575b2e | apaz | 28 September 2022, 00:09:47 UTC | avoid a spurious use-after-realloc warning from gcc [NFC] (#46923) Co-authored-by: apaz-cli <Aaron.Pazdera@JuliaComputing.com> | 28 September 2022, 00:09:47 UTC |
6db1006 | Keno Fischer | 27 September 2022, 22:09:51 UTC | irinterp: Don't try to access undefined phi values (#46930) We don't see this case very often (or at all) on master, because complicated control flow structures are often not eligible for semi-concrete eval. But let's fix it anyway. | 27 September 2022, 22:09:51 UTC |
f1c4d54 | Fredrik Ekre | 27 September 2022, 19:15:51 UTC | Fix shift direction of circshift! for vectors (#46759) This patch fixes the shifting direction for circshift!(x::AbstractVector, n::Integer), which was opposite the direction of circshift(x, n) and circshift!(y, x, n). In addition, this patch fixes the method to also work correctly with offset arrays. Fixes #46533. | 27 September 2022, 19:15:51 UTC |
757f21e | Perry Fraser | 27 September 2022, 17:24:46 UTC | Don't error when transposing an empty buffer (#46925) | 27 September 2022, 17:24:46 UTC |
cda61ef | Keno Fischer | 27 September 2022, 15:48:05 UTC | Inlining: Remove outdated code path for GlobalRef movement (#46880) * Inlining: Remove outdated code path for GlobalRef movement We used to not allow GlobalRef in PhiNode at all (because they could have side effects). However, we then change the IR to make side-effecting GlobalRefs illegal in statement position in general, so now PhiNodes values are just regular value position, so there's no reason any more to try to move GlobalRefs out to statement position in inlining. Moreover, doing so introduces a bunch of unnecesary GlobalRefs that weren't being moved back. We could fix that separately by setting appropriate flags, but it's simpler to just get rid of this special case entirely. * Update test/compiler/inline.jl | 27 September 2022, 15:48:05 UTC |
ff4f86d | Tim Besard | 27 September 2022, 13:47:48 UTC | Fix serialization of code instances. (#46373) If they are encountered in a Julia object directly, as opposed to e.g. during serialization of a method instance, we'll have first populated the backref table as part of jl_serialize_value, so we need to skip that check during code instance serialization. | 27 September 2022, 13:47:48 UTC |
cb46d71 | DilumAluthgeBot | 27 September 2022, 13:20:15 UTC | 🤖 Bump the SuiteSparse stdlib from ed89e0f to e8285dd (#46919) Co-authored-by: Dilum Aluthge <dilum@aluthge.com> | 27 September 2022, 13:20:15 UTC |
418edd3 | Camillo Schenone | 27 September 2022, 11:44:31 UTC | Reorder FileEvent field names in the documentation (#46905) When printing a FileEvent the user sees a text in the format `"path" => FileWatching.FileEvent(bool, bool, bool)` and by reading the documentation the user expect the three booleans to correspond to `changed`, `renamed`, `timedout` while instead the correct order is `renamed`, `changed`, `timedout`. This is just a correction to that. | 27 September 2022, 11:44:31 UTC |
698beed | Tim Holy | 27 September 2022, 09:54:25 UTC | Precompile correct invoke-targets (#46907) This fixes backedge-based invalidation when a precompiled `invoke` is followed by loading a package that adds new specializations for the `invoke`d method. An example is LowRankApprox.jl, where FillArrays adds a specialization to `unique`. | 27 September 2022, 09:54:25 UTC |
6fdcfd4 | Fredrik Ekre | 27 September 2022, 08:37:50 UTC | Update SparseArrays dependency (#46790) This patch updates SparseArrays. In particular it contains https://github.com/JuliaSparse/SparseArrays.jl/pull/260 which is necessary to make progress in #46759. All changes: - Fix ambiguities with Base. (https://github.com/JuliaSparse/SparseArrays.jl/pull/268) - add == for vectors (https://github.com/JuliaSparse/SparseArrays.jl/pull/248) - add undef initializers (https://github.com/JuliaSparse/SparseArrays.jl/pull/263) - Make sure reductions benefit from sparsity (https://github.com/JuliaSparse/SparseArrays.jl/pull/244) - Remove fkeep! from the documentation (https://github.com/JuliaSparse/SparseArrays.jl/pull/261) - Fix direction of circshift (https://github.com/JuliaSparse/SparseArrays.jl/pull/260) - Fix `vcat` of sparse vectors with numbers (https://github.com/JuliaSparse/SparseArrays.jl/pull/253) - decrement should always return a vector (https://github.com/JuliaSparse/SparseArrays.jl/pull/241) - change order of arguments in fkeep, fix bug with fixed elements (https://github.com/JuliaSparse/SparseArrays.jl/pull/240) - Sparse matrix/vectors with fixed sparsity pattern. (https://github.com/JuliaSparse/SparseArrays.jl/pull/201) | 27 September 2022, 08:37:50 UTC |
6c0aa6d | Hendrik Ranocha | 27 September 2022, 06:50:50 UTC | improve type stability of `handle_message(logger, ...` (#46906) | 27 September 2022, 06:50:50 UTC |
8003563 | William Moses | 26 September 2022, 21:35:04 UTC | Don't crash on variable sized gc allocations (#46914) | 26 September 2022, 21:35:04 UTC |
d97f248 | Elliot Saba | 26 September 2022, 18:23:15 UTC | [win] Disable MSYS2 path munging when calling `is.exe` (#46867) Tragically, I believe MSYS2 is messing with options such as `/VERYSILENT` turning them instead into `C:\msys2\VERYSILENT` or similar. | 26 September 2022, 18:23:15 UTC |
26304f7 | Keno Fischer | 26 September 2022, 12:02:57 UTC | lattice: Properly percolate down `tmerge` (#46881) We were skipping the parent lattice of the partials lattice, which may make external lattice implementation nonfunctional. Co-authored-by: Shuhei Kadowaki <40514306+aviatesk@users.noreply.github.com> | 26 September 2022, 12:02:57 UTC |
c0d5ffb | Keno Fischer | 26 September 2022, 07:27:47 UTC | irinterp: Add a hook for control-dependent phi evaluation (#46883) External AbstractInterpreters may want to modify the lattice elements of a phi to track additional information (e.g. by inspecting the branch condition of the idom). Currently, we don't pass enough information down to make this happen, so add a hook function that also takes (ir, idx) and a lazy domtree. Admittedly this is a bit ad-hoc, and would probably be better with some sort of general analysis manager, but this'll do for now. | 26 September 2022, 07:27:47 UTC |
60ee22c | Shuhei Kadowaki | 26 September 2022, 06:51:07 UTC | follow up #46897, improve type stability (#46909) | 26 September 2022, 06:51:07 UTC |
d5cde86 | Lilith Orion Hafner | 25 September 2022, 09:55:10 UTC | Don't prompt field names for tuples at the REPL (#46897) | 25 September 2022, 09:55:10 UTC |
e6d9979 | N5N3 | 24 September 2022, 14:32:19 UTC | Set `intersection = 1` during `intersect_sub_datatype` (#46882) | 24 September 2022, 14:32:19 UTC |
b43bc62 | Tim Holy | 24 September 2022, 13:00:24 UTC | Improve attribution of backedge-triggered invalidation (#46756) SnoopCompile attempts to attribute invalidations to specific causes, but until now it has not generally been able to handle what it called "delayed" invalidations, which arose when a MethodInstance backedge wasn't valid anymore. This dumps more data to the reporting stream and should allow SnoopCompile to assemble the full chain of causes. This also adds invalidation of the backedges of methods that fail to validate their external edges. | 24 September 2022, 13:00:24 UTC |
24cb92d | Jeff Bezanson | 23 September 2022, 06:14:47 UTC | use `invokelatest` to call `REPL.active_module` (#46866) REPL_MODULE_REF might be populated during execution, in which case we won't be able to see REPL methods yet. | 23 September 2022, 06:14:47 UTC |
ea9914e | Shuhei Kadowaki | 22 September 2022, 17:30:59 UTC | add simple test cases for [post-]domination analysis (#46860) | 22 September 2022, 17:30:59 UTC |
45623a8 | Jameson Nash | 22 September 2022, 16:33:49 UTC | staticdata: avoid needing unaligned loads, support 64-bit images (#46683) No functional changes intended here. | 22 September 2022, 16:33:49 UTC |
15f8fad | Lilith Orion Hafner | 22 September 2022, 11:10:48 UTC | Uncomment out bitset test (#46847) | 22 September 2022, 11:10:48 UTC |
a959ed8 | Keno Fischer | 22 September 2022, 09:29:13 UTC | Fix small logic bug in finalizer inlining Found while testing bigger examples. Fixes the logic introduced in #46651 | 22 September 2022, 09:29:13 UTC |
e636342 | Keno Fischer | 22 September 2022, 09:28:25 UTC | Add assume_fatal_throw optimizer option (#46856) This option frees the optimizer from having to prove nothrow in order to move certain side effects across call sites. It is currently enabled in finalizer inlining, but there may be opportunities to use it elsewhere in the future, as well as potentially plumbing it down to LLVM. The intended use case is not in the main compilation pipeline, but rather for alternative compilation modes where thrown errors are fatal and the state of the heap can not be observed after a thrown error. | 22 September 2022, 09:28:25 UTC |
70fa9b1 | Valentin Churavy | 22 September 2022, 06:15:36 UTC | Update to 14.0.6+0 (#46842) | 22 September 2022, 06:15:36 UTC |
892f76e | Ian Atol | 22 September 2022, 04:32:15 UTC | Minor cleanup to follow up 45062 (#46832) | 22 September 2022, 04:32:15 UTC |
62ac26a | Shuhei Kadowaki | 21 September 2022, 22:59:37 UTC | inlining: relax `finalizer` inlining control-flow restriction (#46651) Eager `finalizer` inlining (#45272) currently has a restriction that requires all the def/uses to be in a same basic block. This commit relaxes that restriction a bit by allowing def/uses to involve control flow when all of them are dominated by a `finalizer` call to be inlined, since in that case it is safe to insert the body of `finalizer` at the end of all the def/uses, e.g. ```julia const FINALIZATION_COUNT = Ref(0) init_finalization_count!() = FINALIZATION_COUNT[] = 0 get_finalization_count() = FINALIZATION_COUNT[] @noinline add_finalization_count!(x) = FINALIZATION_COUNT[] += x @noinline Base.@assume_effects :nothrow safeprint(io::IO, x...) = (@nospecialize; print(io, x...)) mutable struct DoAllocWithFieldInter x::Int end function register_finalizer!(obj::DoAllocWithFieldInter) finalizer(obj) do this add_finalization_count!(this.x) end end function cfg_finalization3(io) for i = -999:1000 o = DoAllocWithFieldInter(i) register_finalizer!(o) if i == 1000 safeprint(io, o.x, '\n') elseif i > 0 safeprint(io, o.x) end end end let src = code_typed1(cfg_finalization3, (IO,)) @test count(isinvoke(:add_finalization_count!), src.code) == 1 end let init_finalization_count!() cfg_finalization3(IOBuffer()) @test get_finalization_count() == 1000 end ``` To support this transformation, the domtree code also gains the ability to represent post-dominator trees, which is generally useful. | 21 September 2022, 22:59:37 UTC |
72be01b | pchintalapudi | 21 September 2022, 22:10:49 UTC | Insert bitcast after any additional phi nodes (#46854) Adjust bitcast insertion point to after any phi nodes | 21 September 2022, 22:10:49 UTC |
ff62f84 | DilumAluthgeBot | 21 September 2022, 21:50:07 UTC | 🤖 Bump the NetworkOptions stdlib from 4d3df64 to 8ce1e10 (#46853) Co-authored-by: Dilum Aluthge <dilum@aluthge.com> | 21 September 2022, 21:50:07 UTC |
2bd5a44 | pchintalapudi | 21 September 2022, 17:49:24 UTC | Track JITLink-allocated bytes (#46823) * Track JITLink-allocated bytes * Address review formatting | 21 September 2022, 17:49:24 UTC |
d093a1a | Keno Fischer | 21 September 2022, 15:36:21 UTC | Remove unused optimizer params (#46848) | 21 September 2022, 15:36:21 UTC |
d4f0567 | Jameson Nash | 21 September 2022, 13:01:33 UTC | dump: implement cycle handling in has_backedge_to_worklist (#46749) | 21 September 2022, 13:01:33 UTC |
ed01ee0 | Jameson Nash | 21 September 2022, 11:27:34 UTC | ccall: handle Union appearing as a field-type without crashing (#46787) We disallow union as the direct type, so perhaps we should disallow it as a field-type also, but since we do allow references in those cases typically, we will allow this also. Also DRY the emit_global code, since it had bit-rotted relative to the usual code path through emit_globalref (and apparently could still be run though for handling the first argument to cfunction). Fix #46786 | 21 September 2022, 11:27:34 UTC |
bb7c7eb | Jameson Nash | 21 September 2022, 11:27:15 UTC | [GCChecker] report FunctionDecl and type for missing JL_NOTSAFEPOINT calls (#46834) In C++, some calls are implicit, which makes the call alone ambiguous and the message unclear. This helps clarify it. | 21 September 2022, 11:27:15 UTC |
91d8e38 | Jameson Nash | 21 September 2022, 11:26:57 UTC | inference: remove allocation hot-spot exposed by Profile.Allocs examination (#46843) This Union{Pair,Nothing} accounted for several % of total inference allocations, and might stack-overflow on very large numbers of basic blocks with very unusual structures. | 21 September 2022, 11:26:57 UTC |
d7158dc | Mason Protter | 21 September 2022, 01:28:02 UTC | Update interfaces.md (#46833) AbstractArrays have never been required to be mutable, and we have many subtypes of `AbstractArray` in `Base` and `LinearAlgebra` that do not implement `setindex!` since they are immutable, or only implement it for a subset of their indices (e.g. `CartesianIndices`, the various range types, `Symmetric`, `Hermitian`, `Diagonal`, ). There is also a lot of hope and plans for more immutable, dynamic array support from Base, and of course a rich set of immutable arrays out there in the package ecosystem which do not have `setindex!` | 21 September 2022, 01:28:02 UTC |
ffa76f9 | Udoh Jeremiah | 21 September 2022, 01:26:00 UTC | consistency on typemax and typemin docs (#46827) * consistency on typemax and typemin docs The `typemax` and `typemin` docs isn't consistent with each other on its examples and `see also` section (see reasons below). While this isn't an issue when looking up the function with `help>` to work with integers, for floating-point types, its a big deal because: - On the `typemax` examples, there is a very good example there with a great comment, pointing users on to look into `floatmax`, if `typemax` doesn't serves them; but the `typemin` doesn't have this - which isn't great, since both `typemax` and `typemin` have great use. - The `see also` section on `typemax` point users to other available functions which might prove or introduce other points to consider if `typemax` isn't what they're looking for; for `typemin`, this isn't present. I provided examples on integers, just so the function isn't thought of like working for only floating points. Moreover, I feel like the current docs were written assuming users would always lookup `typemin` and `typemax` in `help>`, before using anyone of them. Most time this is true, but I think it's best not to assume. | 21 September 2022, 01:26:00 UTC |
67f994c | Keno Fischer | 20 September 2022, 23:11:31 UTC | Fix SROA miscompile in large functions (#46819) * Fix SROA miscompile in large functions During the development of #46775, we saw a miscompile in the compiler, specifically, we saw SROA failing to provide a proper PHI nest. The root cause of this turned out to be an incorrect dominance query. In particular, during incremental compaction, the non-compacted portion of the IncrementalCompact cfg is allocated, but not valid, so we must not query it for basic block information. Unfortunately, I don't really have a good test case for this. This code has grown mostly organically for a few years, and I think it's probably overdue for an overhaul. * optimizer: address TODO for computing `joint_effects` more efficiently Co-authored-by: Shuhei Kadowaki <aviatesk@gmail.com> | 20 September 2022, 23:11:31 UTC |
caf544b | pchintalapudi | 20 September 2022, 17:02:56 UTC | Deduplicate lifted PHI node edges (#46662) * Deduplicate lifted PHI node edges * Add gc lowering test * Simplify and clean up test case * Remove assertion for now | 20 September 2022, 17:02:56 UTC |
276af84 | Udoh Jeremiah | 20 September 2022, 12:57:34 UTC | use native Julia code in round example (#46841) | 20 September 2022, 12:57:34 UTC |
89c4a2a | Tim Besard | 20 September 2022, 07:05:38 UTC | Merge pull request #46796 from JuliaLang/tb/libuv Expose constrained memory limits and have the GC use them. | 20 September 2022, 07:05:38 UTC |
b6d2434 | Kristoffer Carlsson | 20 September 2022, 06:07:35 UTC | set number of openblas threads to 1 while precompiling (#46792) | 20 September 2022, 06:07:35 UTC |
417cdca | Udoh Jeremiah | 20 September 2022, 03:38:18 UTC | clear info on the exponent function (#46815) Co-authored-by: Daniel Karrasch <daniel.karrasch@posteo.de> | 20 September 2022, 03:38:18 UTC |
88ec96a | Shuhei Kadowaki | 20 September 2022, 00:21:13 UTC | compiler: some minor NFC clean-ups (#46835) | 20 September 2022, 00:21:13 UTC |
d354662 | Tim Besard | 19 September 2022, 12:10:03 UTC | Adapt GC to new APIs. | 19 September 2022, 20:28:53 UTC |
00f8938 | Tim Besard | 16 September 2022, 14:33:30 UTC | Expose constrained memory as Sys.(total|free)_memory; add Sys.physical_(total_free)_memory. | 19 September 2022, 20:28:53 UTC |
22f8faf | Tim Besard | 16 September 2022, 09:43:44 UTC | Bump libuv. | 19 September 2022, 20:25:20 UTC |
8af6731 | Kristoffer Carlsson | 19 September 2022, 13:13:19 UTC | typeassert `get` from `IOContext` (#46828) | 19 September 2022, 13:13:19 UTC |
eea2ca7 | Kristoffer Carlsson | 19 September 2022, 11:42:03 UTC | elaborate on how to check `:compact` on `IOContext` (#46826) * elaborate on how to check `:compact` on `IOContext` Co-authored-by: Shuhei Kadowaki <40514306+aviatesk@users.noreply.github.com> | 19 September 2022, 11:42:03 UTC |
21e8c7c | Kristoffer Carlsson | 19 September 2022, 08:16:31 UTC | Merge pull request #46781 from JuliaLang/kc/output_prompts Redo of "Add ability to add output prefixes to the REPL output and use that to implement an IPython mode" | 19 September 2022, 08:16:31 UTC |
16e9f4b | Shuhei Kadowaki | 19 September 2022, 01:35:40 UTC | follow up #46775, add missing annotations (#46817) | 19 September 2022, 01:35:40 UTC |
f794bdd | Shuhei Kadowaki | 18 September 2022, 10:14:10 UTC | follow up #46799, add test case for `CachedMethodTable` (#46818) | 18 September 2022, 10:14:10 UTC |
86e0c6a | Udoh Jeremiah | 18 September 2022, 01:00:01 UTC | fix typo on TwicePrecision docs (#46813) | 18 September 2022, 01:00:01 UTC |
433b11f | Shuhei Kadowaki | 18 September 2022, 00:49:25 UTC | NFC: simplify the default `limit` setting of `Core.Compiler.findall` (#46809) Use `limit=-1` instead of `limit=Int(typemax(Int32))`. | 18 September 2022, 00:49:25 UTC |
b3f25d7 | Keno Fischer | 17 September 2022, 22:01:55 UTC | inlining: Also apply statement effects when declining to inline (#46775) * inlining: Also apply statement effects when declining to inline When inlining, we already determine what the effects for all the different cases are, so that we can apply appropriate statement flags on each of the edges. However, if for some reason we decided to decline to inline, we weren't making use of this information. Fix that. * make it work. Co-authored-by: Shuhei Kadowaki <aviatesk@gmail.com> | 17 September 2022, 22:01:55 UTC |
b6cabf3 | Keno Fischer | 17 September 2022, 22:01:06 UTC | Use more of the actual inliner in finalizer inlining (#46753) * Use more of the actual inliner in finalizer inlining Currently the special-case inliner for finalizer generated incorrect code for unmatched sparams (which we had a test for, but which was unfortunately broken) and varargs (which we did not have a test for). Of course, we handle these cases correctly in actual inlining, so do some light refactoring to share more code between the two inlining paths. * Update base/compiler/ssair/inlining.jl Co-authored-by: Ian Atol <ian.atol@juliacomputing.com> Co-authored-by: Ian Atol <ian.atol@juliacomputing.com> | 17 September 2022, 22:01:06 UTC |
defc396 | Elliot Saba | 17 September 2022, 17:36:26 UTC | Disable MSYS2's path munging for `stringreplace` (#46803) This was causing our rewriting of the loader's RPATH emulation to fail after running `make install`, as MSYS2 was rewriting our list that looks like: ``` ../bin/libgcc_s_seh-1.dll:../bin/libopenlibm.dll:@../bin/libjulia-internal.dll:@../bin/libjulia-codegen.dll: ``` Into one that looked like: ``` ..\bin\libgcc_s_seh-1.dll;..\bin\libopenlibm.dll;@..\bin\libjulia-internal.dll;@..\bin\libjulia-codegen.dll; ``` By exporting `MSYS2_ARG_CONV_EXCL='*'` for all `stringreplace` invocations, we dodge this issue, as documented by MSYS2 [0]. [0] https://www.msys2.org/wiki/Porting/#filesystem-namespaces | 17 September 2022, 17:36:26 UTC |
c165aeb | Sagnac | 17 September 2022, 12:31:36 UTC | REPL docs: Document existing ^U keybind (#46811) This keybinding currently exists in Julia and is functional, but it wasn't mentioned in the manual. | 17 September 2022, 12:31:36 UTC |
1843ea3 | Udoh Jeremiah | 17 September 2022, 05:49:08 UTC | Typo error on REPL section (#46807) | 17 September 2022, 05:49:08 UTC |
2ef4aba | pchintalapudi | 17 September 2022, 05:47:13 UTC | Changes to support LLVM15 compilation (#46788) | 17 September 2022, 05:47:13 UTC |
e24dd3b | Shuhei Kadowaki | 17 September 2022, 02:59:15 UTC | inference: make `limit::Int` as a caching key of `CachedMethodTable` (#46799) Sometimes `Core.Compiler.findall(::Type, ::CachedMethodTable; limit::Int)` is called with different `limit` setting (in particularity `return_type_tfunc` calls it with `limit=-1`). The query should return different results given different `limit` settings, so its cache should also have different keys per different `limit` settings. fix #46722 | 17 September 2022, 02:59:15 UTC |
81f6c23 | Tim Besard | 16 September 2022, 19:52:42 UTC | Windows build improvements (#46793) * Include unistd.h to silence compilation warning. * Error when running in a MSYS shell. | 16 September 2022, 19:52:42 UTC |
260e986 | pchintalapudi | 16 September 2022, 16:18:04 UTC | Add julia pass pipeline to opt (#46191) * Use NewPM for optimization unless ASAN is in effect * Disable NewPM by default * Add julia pass pipeline to opt * Update llvm devdocs | 16 September 2022, 16:18:04 UTC |
54b4a53 | KristofferC | 24 August 2022, 08:11:10 UTC | add an ipython mode on top of the output prefix functionality | 16 September 2022, 14:01:46 UTC |
03ed550 | Daniel Karrasch | 16 September 2022, 10:50:19 UTC | Remove unnecessary `reducedim_init` specialization (#46777) | 16 September 2022, 10:50:19 UTC |
a7bef77 | Dilum Aluthge | 16 September 2022, 09:46:16 UTC | Make the "system image too large" error message more descriptive (#46570) | 16 September 2022, 09:46:16 UTC |
8c00e17 | Sobhan Mohammadpour | 16 September 2022, 09:43:59 UTC | Fix `mapreduce` on `AdjOrTrans` (#46605) Co-authored-by: Daniel Karrasch <Daniel.Karrasch@posteo.de> Co-authored-by: Daniel Karrasch <Daniel.Karrasch@posteo.de> Co-authored-by: Martin Holters <martin.holters@hsu-hh.de> | 16 September 2022, 09:43:59 UTC |
174b893 | Morten Piibeleht | 16 September 2022, 09:41:22 UTC | doc: guard release branch regex with ^...$ (#46647) | 16 September 2022, 09:41:22 UTC |
0fabe54 | Thomas Christensen | 15 September 2022, 15:29:38 UTC | Help inference of uninferred callers of `read(::IO, ::Type{String})` (#46577) | 15 September 2022, 15:29:38 UTC |
3d3f9ae | KristofferC | 24 August 2022, 07:47:22 UTC | add ability to add an output prefix to the REPL output | 15 September 2022, 14:48:29 UTC |
4026246 | Keno Fischer | 15 September 2022, 14:46:08 UTC | Add effect modeling for Core.compilerbarrier (#46772) The compiler barrier itself doesn't have any effects, though of course by pessimizing type information, it may prevent the compiler from discovering effect information it would have otherwise obtained. Nevertheless, particularly the weaker barriers like `:const` and `:conditional` should not, by themselves taint any effects. | 15 September 2022, 14:46:08 UTC |