textproc/p5-Jq: new port had been added (+)
Jq.pm is a Perl module binding to Jq which inputs and
outputs are Perl data objects that can be represented
as JSON.
[X86] Add WritePack scheduler classes (#240819)
Split off PACKSSUS DW/WB instructions from WriteShuffle class to remove
need for most custom overrides
znver4 - fixes failure to override rm variants to correctly use FPU1/2
pipes like the rr variants
SapphireRapids and C864GM7/8 - still have overrides for their predicated
instructions - best to leave them until #240761 is finalized.
Fixes #240425
editors/xwpe: update to 1.6.9
Switch to the new maintained branch of xwpe.
The project has been (relatively) recently resumed elsewhere by Juan
Manuel Mendez Rey. Most distributions packaging xwpe have already
switched to this repo.
Thanks to zakinko at snowrabbit.org for providing diffs. See pkg/#60821
# CHANGES (since 1.5.30a)
Bugs fixed in 1.6.x:
* Options > Editor: checkboxes and radio buttons could not be ticked in xwpe
(X11) -- fixed (1.6.3). Space, mouse-click and the Alt-<letter> hotkey all
flipped the option's value, but in X11 nothing was drawn, so the box looked
unchanged ("I can't mark it"). Root cause: with NEWSTYLE the dialog redrew
the marks via e_make_xrect_abs -- a 3D bevel in the extbyte overlay whose
checked vs unchecked states differ only by one highlight bit, visually
[1622 lines not shown]
[InstCombine][JumpTableToSwitch] Make a helper for iterating globals elements
Currently there are at least two folds/passes that read elements of a constant
global:
- instcombine's `foldCmpLoadFromIndexedGlobal`
- jump-table-to-switch, when reading the functions from a jump table
and a third one is being written for simplifycfg in PR #229035.
The code to do that is not trivial, especially in its most general form. The
two implementation above currently have different limitations, and PR #229035
has yet another buggy and limited implementation of it.
This PR adds a helper class `ConstGlobalIterator` that analyzes a load from a
global and allows iterating the accessed elements. Current implementation is a
copy of the instcombine's: that's the most general version we have today
(though even that has limitations, e.g. it gives up when the stride is smaller
than the load size).
[11 lines not shown]
[InstCombine] Simplify foldCmpLoadFromIndexedGlobal calls (NFC)
Instead of checking the load's address operand at each call site, check
it once in foldCmpLoadFromIndexedGlobal.
Pull up following revision(s) (requested by riastradh in ticket #1413):
sys/external/bsd/drm2/dist/drm/i915/gem/i915_gem_pages.c: revision 1.8
i915: Fix null pointer deref in i915_gem_object_get_dma_address.
Matches the Linux code in the #else this way.
PR kern/60755: i915drmkms crashes on Intel Bay Trail GPU making the
machine rebooting
Pull up following revision(s) (requested by riastradh in ticket #570):
sys/external/bsd/drm2/dist/drm/i915/gem/i915_gem_pages.c: revision 1.8
i915: Fix null pointer deref in i915_gem_object_get_dma_address.
Matches the Linux code in the #else this way.
PR kern/60755: i915drmkms crashes on Intel Bay Trail GPU making the
machine rebooting
Pull up following revision(s) (requested by riastradh in ticket #1412):
sys/external/bsd/drm2/dist/drm/nouveau/nouveau_fence.c: revision 1.19
nouveau: Don't set dma fence error if already signaled.
This happens asynchronously on hardware error. Upstream Linux trips
WARN_ON in this case; our dma_fence_set_error trips KASSERT instead.
We could maybe switch dma_fence_set_error to use WARN_ON too but it's
probably better not to take this path anyway -- this assertion trips
on logic that is incoherent, if not outright wrong.
PR kern/58745: nouveau triggered assert in linux_dma_fence.c
Pull up following revision(s) (requested by riastradh in ticket #569):
sys/external/bsd/drm2/dist/drm/nouveau/nouveau_fence.c: revision 1.19
nouveau: Don't set dma fence error if already signaled.
This happens asynchronously on hardware error. Upstream Linux trips
WARN_ON in this case; our dma_fence_set_error trips KASSERT instead.
We could maybe switch dma_fence_set_error to use WARN_ON too but it's
probably better not to take this path anyway -- this assertion trips
on logic that is incoherent, if not outright wrong.
PR kern/58745: nouveau triggered assert in linux_dma_fence.c
[mlir] Add LabelLike trait for blocks entered without a CFG edge
Some ops mark a block that control enters through a jump the CFG does
not show yet. ClangIR's cir.label is the target of cir.goto, which may
leave a region and only becomes a branch once the CFG is flattened.
Such a block often has no predecessors, so eraseUnreachableBlocks
deletes it and the greedy driver skips its ops.
This adds OpTrait::LabelLike for an op that starts a non-entry block,
and findLabelEntry, which returns the op where control enters a block
through a label. That is either the label itself or an op whose regions
contain one, unless that op, or one between it and the label, is
isolated from above.
eraseUnreachableBlocks keeps these blocks, the blocks they reach and the
blocks whose values they use. Region DCE treats every remaining block as
live, and cf.br does not merge a labeled block into its predecessor.
GreedyRewriteConfig::enableRewritingAfterLabels, off by default, lets
[7 lines not shown]
Pull up following revision(s) (requested by riastradh in ticket #1411):
sys/external/bsd/drm2/dist/drm/i915/gt/intel_lrc.c: revision 1.10
sys/external/bsd/drm2/dist/drm/i915/gt/intel_lrc.c: revision 1.9
i915: Fix execlist submission register indexing.
PR port-amd64/58657: i915drmkms blank screen
i915: Fix execlist submission register indexing harder.
This time, with any luck, I transcribed the indexing correctly.
PR port-amd64/58657: i915drmkms blank screen
Pull up following revision(s) (requested by riastradh in ticket #568):
sys/external/bsd/drm2/dist/drm/i915/gt/intel_lrc.c: revision 1.10
sys/external/bsd/drm2/dist/drm/i915/gt/intel_lrc.c: revision 1.9
i915: Fix execlist submission register indexing.
PR port-amd64/58657: i915drmkms blank screen
i915: Fix execlist submission register indexing harder.
This time, with any luck, I transcribed the indexing correctly.
PR port-amd64/58657: i915drmkms blank screen
loader.efi: Clear the zstd stream pointer in zstd_fini()
do_download_ramdisk() calls decomp_fini() a second time to free the buffer when
it gives up after a finished download, so zstd freed its strem twice and libsa
libsa panicked. Clear the pointer like xz_fini().
Reported by: llm-postcr
Reviewed by: imp
Approved by: imp
Fixes: afee781523e4 ("loader.efi: Recognize new memdisk=<url> and memcd=<url> options")
Sponsored by: Netflix
[mlir][bufferization] Do not hoist copying allocations to out-params (#242630)
With `hoist-static-allocs` enabled, `-buffer-results-to-out-params`
replaces returned allocations with caller-provided output buffers and
erases their defining operations. Checking only `AllocationOpInterface`
also matches `memref.realloc` and `bufferization.clone`, whose results
preserve or reproduce existing data. Erasing these operations loses that
data and leaves the output buffer partially or entirely uninitialized.
Require `getHoistingKind() != HoistingKind::None` before replacing an
allocation. `memref.realloc` (`None` since #231608) and
`bufferization.clone` (`None` by default) are retained. For the static
results in #242611, the pass copies their contents into the output
parameters through the existing fallback path. `memref.alloc` remains
eligible for replacement.
The check remains interface-based, preserving support for custom
allocation operations introduced in #120288. Such operations remain
eligible when they report a non-None hoisting kind.
[12 lines not shown]
[lld/mac] Claim per-file work one item at a time (#242765)
This ports #240094 to lld/MachO.
Relocation processing in lld/MachO doesn't need an index, so this can
use parallelForFineGrained instead of parallelForSharded() in lld/ELF.
Linking Chromium Framework on an M4 Max (time trace scopes, median of
7):
Parse relocations: 115 ms -> 75 ms
Apply linker optimization hints: 36 ms -> 22 ms
Total link (hyperfine, median of 15): 3.911 s -> 3.859 s
No behavior change.
Pull up following revision(s) (requested by riastradh in ticket #1410):
sys/kern/kern_exec.c: revision 1.536
sys/kern/kern_fork.c: revision 1.237
sys/rump/librump/rumpkern/lwproc.c: revision 1.60
fork, posix_spawn: Avoid race with setsid/setpgid.
PR kern/60962: fork and spawn read p_pgrp without proc_lock
rump: Copy struct proc::p_pgrp explicitly
Now that it's not in p_startcopy/endcopy, the memcpy isn't enough.
Should fix the thousands of test failures I caused by moving p_pgrp
out of the p_startcopy/endcopy range!
PR kern/60962: fork and spawn read p_pgrp without proc_lock
[mlir][docs] Add guidance on "non observable" side effect modeling (#242620)
Mention that a dialect defines which aspects of execution are observable
and which are
implementation details outside that semantic model. Also add a few
examples.
Discussion:
https://discourse.llvm.org/t/guidance-on-not-observable-side-effect-modeling/92790
Assisted-by: Codex
devel/electron45: Add port: Build cross-platform desktop apps with JavaScript, HTML, and CSS
Build cross platform desktop apps with JavaScript, HTML, and CSS.
It's easier than you think.
If you can build a website, you can build a desktop app. Electron is a
framework for creating native applications with web technologies like
JavaScript, HTML, and CSS. It takes care of the hard parts so you can
focus on the core of your application.
WWW: https://electronjs.org/
Pull up following revision(s) (requested by riastradh in ticket #567):
sys/kern/kern_exec.c: revision 1.536
sys/kern/kern_fork.c: revision 1.237
sys/rump/librump/rumpkern/lwproc.c: revision 1.60
fork, posix_spawn: Avoid race with setsid/setpgid.
PR kern/60962: fork and spawn read p_pgrp without proc_lock
rump: Copy struct proc::p_pgrp explicitly
Now that it's not in p_startcopy/endcopy, the memcpy isn't enough.
Should fix the thousands of test failures I caused by moving p_pgrp
out of the p_startcopy/endcopy range!
PR kern/60962: fork and spawn read p_pgrp without proc_lock
