[MLIR][Python][NFC] Refine the docstring of `PassManager.add(callable, ..)` (#173945)
This PR expands the docstring for `PassManager.run(callable, ..)` by
adding descriptions for each parameter, making it easier for users to
understand. No functional change.
vm_object_coalesce(): return swap reservation back if overcharged
It is possible for both vm_map_insert() and vm_object_coalesce() to charge
both for the same region. The issue is that vm_map_insert() must charge
in advance to ensure that the mapping would not exceed the swap limit,
but then the coalesce might decide to extend the object, and already
(partially) backs the mapped region.
Handle this by passing to vm_object_coalesce() exact information about
the charging mode of the extending range 'not charging', 'charged' using
flags instead of simple boolean. In vm_object_coalesce(), detect
overcharge and undo it if needed.
Note that this relies on vm_object_coalesce() call being the last action
in vm_map_insert() before extending the previous map entry.
Reported and tested by: pho
Reviewed by: markj
Sponsored by: The FreeBSD Foundation
[2 lines not shown]
vm_object_coalesce(): do not account holes twice
alc wrote:
Suppose that the object is OBJ_ONEMAPPING and that we, in fact,
have a single mapping to it. Then, we punch a hole in that mapping.
vm_map_entry_delete() only subtracts from the object's charge when
we shrink the size of the object. Now, suppose that we perform
mmap(MAP_ANON) to reallocate some of the hole. Aren't we going to add to
the charge here, even though vm_map_entry_delete() never subtracted from
the charge for the hole that was created?
Only account the change in the charged object size that was added to it.
Noted by: alc
Reviewed by: alc, markj
Tested by: pho
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D54263
[TableGen] Tweak whitespace printing in DAGISelMatcherEmitter to avoid trailing whitespace in output.
The main offender was the trailing space in EmitVBRValue, but there
were a few other issues.
[MLIR][Python] Refine the support of `RewritePatternSet.add` (#173874)
This patch includes the following changes:
- `RewritePatternSet.add` now accepts op name (e.g. `.add("arith.addi",
fn)`) besides op class (e.g. `.add(arith.AddIOp, fn)`)
- add a concrete signature and a more complete docstring to
`RewritePatternSet.add`.
plasma6-plasma-activities-stats: add version 6.5.2
The KActivitiesStats library provides a querying mechanism for the data
that the activity manager collects - which documents hae been opened by
which applications, and what documents have been linked to which activity.
The activity manager also keeps the score for each document which gets
higher when a particular document has been often accessed or kept open
for longer periods of time. This score is also available through the
querying mechanism.
qcoro: add version 0.12.0
QCoro provides the tools necessary to make easy use of C++20 coroutines with
Qt. The cornerstone of the library is `QCoro::Task<T>`, which represents an
executed coroutine and allows the result of the coroutine to be asynchronously
awaited by its caller. Additionally, QCoro provides a set of wrappers for
common Qt types, such as `QTimer`, `QNetworkReply`, `QDBusPendingCall`,
`QFuture` and others, that allow to `co_await` their asynchronous operations
directly.
