[VPlan] Simplify&clarify skipping VPValues in calculateRegisterUse (NFC)
Split off as suggested in https://github.com/llvm/llvm-project/pull/156262/.
This refactors the code to clarify comments and code, in preparation for #156262.
[PowerPC] Use lxvp/stxvp for mcpu=future v256i1 types (#184447)
For `-mcpu=future`, add patterns to use paired vector instructions
(lxvp/lxvpx/stxvp/stxvpx)
for v256i1 operations instead of splitting into two separate vector
operations.
Assistend by AI.
[lldb][Module] Remove feedback_stream parameter from LoadScriptingResources (#186787)
I'm in the process of making `LoadScriptingResources` interactively ask
a user whether to load a script. I'd like to turn the existing warning
into the prompt. The simplest way to achieve this is to not print into a
`feedback_stream` parameter, and instead create a prompt right there.
This patch removes the `feedback_stream` parameter and emits a
`ReportWarning` instead. If we get around to adding the prompt instead
of the warning, those changes will be simpler to review. But even if we
don't end up replacing the warning with a prompt, moving away from
output parameters and towards more structured error reporting is a
nice-to-have (e.g., the `warning` prefix is now colored, IDEs have more
flexibility on how to present the warning, etc.).
For a command-line user nothing should change with this patch (apart
from `warning:` being highlighted).
[mlir][llvmir][OpenMP] Translate affinity clause in task construct to llvmir (#182223)
Translate affinity entries to LLVMIR by passing affinity information to
createTask (__kmpc_omp_reg_task_with_affinity is created inside
PostOutlineCB).
3/3 in stack for implementing affinity clause with iterator modifier
1/3 #182218
2/3 #182222
3/3 #182223
NAS-140206 / 26.0.0-BETA.2 / Clarify code comments and logging messages related to disk retaste (by themylogin) (#18460)
The root cause of the hanging job issue was removing
`multiprocessing.set_start_method('spawn')` when process pool was
removed. This is confirmed by the absence of the bug in 26.0.0-BETA.1
where process pool is still present.
Original PR: https://github.com/truenas/middleware/pull/18446
Co-authored-by: themylogin <themylogin at gmail.com>
kernel_lock_spinout: fix an assertion failure
it's possible for the calling lwp to be preempted in the middle
of this function and migrated to the "holder" cpu.
this commit would fix the following crash seen on my qemu/nvmm VM
on a busy host:
```
[ 36199.6483272] cpu0[1851 nbxz]: kernel lock spinout
[ 36199.6483272] panic: kernel diagnostic assertion "curcpu() != ci" failed: file "/root/git/netbsd-src/sys/kern/subr_ipi.c", line 358
[ 36199.6483272] cpu0: Begin traceback...
[ 36199.6483272] vpanic() at netbsd:vpanic+0x189
[ 36199.6634956] kern_assert() at netbsd:kern_assert+0x4b
[ 36199.6634956] ipi_unicast() at netbsd:ipi_unicast+0x1a2
[ 36199.6634956] _kernel_lock() at netbsd:_kernel_lock+0x254
[ 36199.6634956] bdev_strategy() at netbsd:bdev_strategy+0xab
[ 36199.6634956] spec_strategy() at netbsd:spec_strategy+0x77
[ 36199.6634956] VOP_STRATEGY() at netbsd:VOP_STRATEGY+0x3c
[ 36199.6755210] uvm_swap_io() at netbsd:uvm_swap_io+0x2c1
[8 lines not shown]
zfs: fix zfs_range_lock_try
the change "zfs: add zfs_range_lock_try" was incomplete.
i've observed the following deadlock:
```
db{0}> tr /a ffff96777f74f400
trace: pid 0 lid 125 at 0xffffce80c3203b50
sleepq_block() at netbsd:sleepq_block+0xf4
cv_wait() at netbsd:cv_wait+0xca
pool_grow() at netbsd:pool_grow+0x47b
pool_get() at netbsd:pool_get+0xae
pool_cache_get_slow() at netbsd:pool_cache_get_slow+0x136
pool_cache_get_paddr() at netbsd:pool_cache_get_paddr+0x27d
kmem_intr_alloc() at netbsd:kmem_intr_alloc+0x13c
kmem_alloc() at netbsd:kmem_alloc+0x2a
zfs_range_lock_impl() at zfs:zfs_range_lock_impl+0x30
zfs_netbsd_putpages() at zfs:zfs_netbsd_putpages+0x1c0
VOP_PUTPAGES() at netbsd:VOP_PUTPAGES+0x43
[6 lines not shown]
[mlir][linalg][elementwise] Fold broadcast into new elementwise (#167626)
Fold broadcast into new elementwise Op which has affine-map attached.
Merging on behalf of @someoneinjd
[libc] Fix llvm-gpu-loader passing uninitialized device memory (#186804)
Summary:
The return value was not zeroed, this was accidentally dropped when we
did the port and it's zero "almost always" so I didn't notice. Hopefully
this makes the test suite no longer flaky.
[flang] Reorder messages wrt line number before diff(actual, expect)
When messages are attached together, the source locations to which they
refer are not necessarily monotonically increasing. For example
```
error: foo.f90:10: There is a problem here # line 10
because: foo.f90:12: This thing is invalid # line 12 (attached)
error: foo.f90:11: There is another problem here # line 11
```
There is no way to represent that in the source flle via ERROR annotations,
so before running unified_diff "canonicalize" the list of messages into an
order that corresponds to the line numbers.
[Flang][OpenMP] Provide option to use heap allocation for private adjustable arrays (#186795)
The size of adjustable Fortran arrays is not known at compilation time.
Using limited GPU stack memory may cause hard-to-debug errors. On the
other hand, switching to heap memory allocation may lead to missed
optimization opportunities and significantly increased kernel execution
time.
Adding the option `-mmlir --enable-gpu-heap-alloc` allows the user to
generate valid code for adjustable Fortran arrays. The flag is off by
default, so there is no efficiency penalty for code that does not use
adjustable arrays.
[SPIR-V] Fix llvm.spv.gep return type for vector-indexed GEPs (#185931)
The `int_spv_gep` intrinsic was defined with `llvm_anyptr_ty` which
forced it to return a scalar pointer. Change the return type to
`llvm_any_ty` to allow the intrinsic to match the actual result type of
the original GEP, whether scalar or vector
