[lldb] Report a scripted frame's variables with the frame's value type (#221708)
A scripted frame's variable exists as two objects: a Variable holding
the scope the frame assigned it, and a ValueObject holding what the
frame built. SBValue::GetValueType() reports the ValueObject's, and
GetValueObjectForFrameVariable handed that ValueObject back unchanged,
so the scope never reached a client. A ValueObject built in Python is a
ValueObjectConstResult, which reports how it was produced rather than
which variable it stands for, leaving anything that groups a frame's
variables by scope unable to place it. `frame variable` was unaffected
because it reads the Variables directly.
This patch presents the ValueObject under that scope instead. A class
for this already existed as ValueObjectRecognizerSynthesizedValue, which
frame recognizers use to name an argument: both take a ValueObject that
cannot report the ValueType it is being presented as and supply that
ValueType for it, so generalize that one into
ValueObjectSynthesizedValue and use it for both. ValueObjectVariable is
the other class that pairs a ValueObject with a ValueType, but it cannot
[28 lines not shown]
Address comments.
Avoid prioritizing DMA and fence candidates while they still have an effective stall.
Make the top-down requirement explicit and remove unreachable bottom-up handling.
[mlir][MathToXeVM] Route math ops by fastmath: native for `afn`, OCL otherwise. (#223816)
The pass had two lowerings for the same math ops. `afn` fastmath ops
went to the OpenCL `native_` intrinsics. Everything else was only
lowered when the `convert-to-ocl` option was set, which defaulted to
off, so those ops were left untouched.
Make `convert-to-ocl` default to true. The fastmath flag now picks the
intrinsic on its own:
- `afn` set -> `__spirv_ocl_native_*`, fast but approximate.
- `afn` unset -> `__spirv_ocl_*`, precise.
`fastmath<fast>` is a group that expands to include `afn`, so it takes
the native path too. Other flags without `afn` do not.
The precedence already worked: the native patterns get a higher pattern
benefit than the precise ones, so an `afn` op still gets the native
intrinsic when both pattern sets are live. Spell the benefits out
[8 lines not shown]
[lldb] Report an error when a debug map object file is missing (#223576)
When an OSO in the debug map does not exist on disk, LLDB records the
load error on the CompileUnitInfo but never surfaces it. The sibling
mod-time-mismatch branch does report, so a stale .o produces a
diagnostic while a deleted one fails silently.
This is easy to hit with LTO. The linker writes the merged object to a
temporary path and deletes it, so unless the build passes
-object_path_lto the debug map points at a file that is already gone.
rdar://162327417
[CI] Use Ubuntu 26.04 for Premerge Image (#223883)
Mainly so that we pull in a newer CMake version given the minimum is
getting bumped soon, but also to get the upgrade over with.
[LLVMABI] Add a union test for two data bytes in the tail eightbyte
One data byte past the first eightbyte narrows the coercion to i8 and two
do not, which the existing tests left implicit. A 10-byte array in a
union with a pointer keeps i64.
Assisted-by: Cursor / claude-opus-5
[CIR] Split side_effect into memory effects, nounwind, and willreturn
side_effect was carrying three facts at once. It described the memory a
callee may touch, and it was also the only thing lowering derived
nounwind and willreturn from, so any callee with a known memory effect
got both. That is wrong for one that can throw, and willreturn had no
other representation in CIR at all.
const and pure now record the three separately, and the enum is replaced
by a structured #cir.memory_effects carrying the same six ModRef slots as
the LLVM dialect. On an operation it prints compactly, as memory(none)
or memory(read, argmem: readwrite). No lowered IR changes.
Assisted-by: Cursor / claude-opus-5
