misc/ompl: Fix duplicate target "post-patch-PLANNERARENA-off"
The .for loop iterated over all options except DEMOS, which included
PLANNERARENA. This generated a post-patch-PLANNERARENA-off target that
conflicted with the explicit one defined after the loop.
Fix by:
- Exempting PLANNERARENA from the .for loop
- Adding the missing PLANNERARENA option variables (DESC, BUILD_DEPENDS,
RUN_DEPENDS) that were previously removed
PR: 295634
Approved by: yuri (maintainer, timeout 2 weeks)
clang/AMDGPU: Split out target ID flags in TranslateArgs.
Change how xnack and sramecc are processed. Introduce
-mxnack/-mno-xnack and -msramecc/-mno-sramecc flags.
When the target is first parsed in TranslateArgs, synthesize
the appropriate flag for the toolchain. This avoids
special case feature string fixups in getAMDGPUTargetFeatures,
and also avoids an extra parse of the target ID.
In the future this will also simplify tracking these ABI
modifiers in a module flag.
As a side-effect, you can use these flags to override the
no specifier case with the flags. These do not fully replace
the target ID syntax, as there's no way to represent compiling
both modes for the same subtarget.
I didn't bother trying to forward these flags on the main command
line without being specified to the offload device, but I suppose
[3 lines not shown]
[mlir][OpenMP] Translate reductions on taskloop
Add LLVM IR translation for reduction and in_reduction clauses on omp.taskloop.context.
For taskloop reduction, emit the implicit taskgroup reduction setup and map each generated task to runtime-provided private reduction storage through __kmpc_task_reduction_get_th_data. For in_reduction, use the same runtime lookup path with a null descriptor to join an enclosing task reduction context.
Unsupported byref, cleanup, and two-argument initializer forms remain diagnosed.
Add MLIR translation tests for the supported taskloop reduction and in_reduction cases.
Import wayland/river 0.4.5, from MAINTAINER Robert Lillack
River is a non-monolithic Wayland compositor: it provides only the
compositor itself, while window-management policy is delegated to an
external client over a custom Wayland protocol. This separation lets
users mix-and-match compositors and window managers.
For a list of window manager supporting the river compositor, please
see: https://codeberg.org/river/wiki/src/branch/main/pages/wm-list.md
ok volker@
[libc++][NFC] Simplify `optional<T>` and `optional<T&>` a bit (#203665)
- Make `optional<T&>`'s iterator base directly from the storage base
instead of inheriting the empty bases, allowing us to remove the
`is_lvalue_reference_v` conditions in the empty bases
- Move the `__is_constructible_for_optional_{meow}` variables closer to
`make_optional` since that's the only place they're really useful for
now
- Change the SFINAE for the iterator availability to use concepts
instead
The above should make it easier to split up in an upcoming patch.
