[Flang][OpenMP] Fix Flang crash and incorrect ordering with OpenMP detached task (#194840)
Fixes - [#194563](https://github.com/llvm/llvm-project/issues/194563)
This PR fixes the runtime crash and incorrect task ordering reported in
the testcase involving:
```
!$omp task if(.false.) depend(out:x) detach(ev)
```
The testcase had two issues:
**1. Segmentation fault near omp_fulfill_event(ev)**
The detach event handle was not being initialized or preserved correctly
before the nested task used it.
**2. Incorrect execution order**
The task with depend(in:x) was running before the detach event was
fulfilled, which violates OpenMP dependency semantics.
#### Changes in this PR
[9 lines not shown]
net/freerdp3: Allow build RDPECAM with CAIRO
Enabling the "RDPECAM" option requires one of the "SWSCALE" or "CAIRO"
options (not just "SWSCALE") - replace "RADIO" with "SINGLE" to force
one of them on and avoid overcomplicating the logic.
PR: 294662
Tested by: Quentin Thébault <quentin.thebault at defenso.fr>
Sponsored by: UNIS Labs
(cherry picked from commit 6edbb9f806b355a559c7b94e9a020f7b1eb13299)
[Flang][OpenMP] Preserve MapInfoOp loc on descriptor base-address maps (#196086)
This PR tries to fix another issue which was discovered after
https://github.com/llvm/llvm-project/issues/195333 was fixed. Now when
we run the same steps, we see the following output
```
omptarget device 0 info: Entering OpenMP data region with being_mapper at test.f90:18:9 with 5 arguments:
omptarget device 0 info: alloc(ptr(1:1024))[48]
omptarget device 0 info: to(ptr(1:1024))[0]
omptarget device 0 info: to(ptr(1:1024))[40]
omptarget device 0 info: to(unknown)[8]
omptarget device 0 info: to(unknown)[4096]
```
Notice "unknown" in the last 2 lines. This happens because
`MapInfoFinalization` splits box descriptor `omp.map.info` ops into a
parent map and a base-address member map (fir.box_offset + inner map
with var_ptr_ptr). The `genBaseAddrMap` used `descriptor.getLoc()` for
those new ops, which dropped the `NameLoc` that lowering attaches for
[6 lines not shown]
[BOLT][AArch64] Refuse to run retpoline insertion pass (#196179)
RetpolineInsertion (`--insert-retpolines`) is specific to X86, but
currently rejects non-X86 targets with an assert. For consistency, this
should be an error message.
- Add a non-X86 guard
- Add the error message to unsupported-passes.test
[BOLT][AArch64] Refuse to run memcpy1 specialization (#196196)
SpecializeMemcpy1 (`--memcpy1-spec=main`) is implemented only for X86.
It does not crash but would be useful to inform the user that it is a
no-op.
- Guard against non-X86
- Add error to unsupported-passes.test
[flang] Remove legacy (non-HLFIR) lowering options from tests (#196137)
Update flang LIT tests to drop references to compiler options that
controlled legacy non-HLFIR lowering: `-flang-experimental-hlfir`,
`-flang-deprecated-no-hlfir`, the bbc `-hlfir`/`--hlfir` switch, and
`--use-desc-for-alloc=false`. The dropped flags were either no-ops or
selected behavior that is now the only supported lowering path.
Delete `Driver/hlfir-no-hlfir-error.f90`, which existed solely to test
mutual exclusion of `-flang-experimental-hlfir` and
`-flang-deprecated-no-hlfir`.
This commit contains only test changes; the option/code removal will be
done in separate commits.
Assisted-by: AI
[lldb] Trim and show embedded zeros in `charN_t` arrays (#195514)
When formatting `char[N]` (N > 0), the read buffer is limited to the
array size and trailing zeros are trimmed.
`charN_t[N]` was treated like a `charN_t *` and the formatter read until
the first zero byte.
If the array doesn't have any zero bytes in it, this will read too much.
If the array has zero bytes in it, it will show too little.
With this PR, `wchar_t[N]` and `charN_t[N]` are printed like `char[N]`.
security/vuxml: Add mongodb vulnerabilities
CVE-2026-6914
Base Score: 7.5 HIGH
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVE-2026-6915
Base Score: 4.3 MEDIUM
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Fix treat as withdraw handling for invalid ORIGIN attributes
If a prefix triggers the F_ATTR_PARSE_ERR case and therefor a RFC 7606
treat as withdraw rde_attr_parse() needs to return a success and not -1.
The return (-1) was missed when the RFC 7606 handling was added.
Move the F_ATTR_ORIGIN marker up to be more in line with other attributes.
OK tb@
[MLIR][ODS] Add strict property assembly format mode
Introduce a dialect-level ODS flag for strict property handling in declarative
assembly formats. It is disabled by default for now, preserving existing parser
behavior unless a dialect opts in.
Enable the mode immediately for dialects whose declarative assembly formats
already satisfy these binding rules.
When enabled, a property-backed op format must bind every inherent attribute
and property directly or include prop-dict.
Generated parsers for opted-in dialects also reject inherent attributes that
arrive through attr-dict, preventing Operation::setAttrs from populating
properties through that path.
Add mlir-tblgen coverage and document default and strict dialect behavior.
Assisted-by: Codex
Fix two memory accounting issues in chash
- ch_table_resize() did not increase the global cc_num_extendible value
- ch_sub_free() can be called with NULL pointer arguments and in that
case the accounting must be skipped
OK tb@
Use simpler logic to ensure path_id_tx is never 0
There is a theoretical case where the 0 conflict would be missed if
this arc4random() returned 0 for the first peer.
OK tb@
