[all-commits] [llvm/llvm-project] 147bf7: [lldb-dap][test] Fix stackTrace test in symlink en...

Aiden Grossman via All-commits all-commits at lists.llvm.org
Tue Jul 14 18:06:06 PDT 2026


  Branch: refs/heads/users/boomanaiden154/lit-remove-external-shell-tests-for-shtest-format
  Home:   https://github.com/llvm/llvm-project
  Commit: 147bf7102fdcd4d016c6d214ff9924c9fa3ee215
      https://github.com/llvm/llvm-project/commit/147bf7102fdcd4d016c6d214ff9924c9fa3ee215
  Author: Jordan Rupprecht <rupprecht at google.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M lldb/test/API/tools/lldb-dap/stackTrace/TestDAP_stackTrace.py

  Log Message:
  -----------
  [lldb-dap][test] Fix stackTrace test in symlink environment (#209595)

This test (edited in #209236) fails when run in an environment where
source files are symlinks. Using `realpath` breaks that, as we use the
path in assertions later. The var is already constructed as `source_file
= self.getSourcePath("main.c")` which should be sufficient for
`_RecurseSource()` to work.


  Commit: ef118b5b3a617237729b010b944237c146e8d300
      https://github.com/llvm/llvm-project/commit/ef118b5b3a617237729b010b944237c146e8d300
  Author: Jan Korous <jkorous at apple.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    A clang/include/clang/ScalableStaticAnalysis/Analyses/SharedLexicalRepresentation/SharedLexicalRepresentation.h
    M clang/include/clang/ScalableStaticAnalysis/BuiltinAnchorSources.def
    M clang/lib/ScalableStaticAnalysis/Analyses/CMakeLists.txt
    A clang/lib/ScalableStaticAnalysis/Analyses/SharedLexicalRepresentation/SharedLexicalRepresentationFormat.cpp
    M clang/unittests/ScalableStaticAnalysis/CMakeLists.txt
    A clang/unittests/ScalableStaticAnalysis/Serialization/JSONFormatTest/SharedLexicalRepresentationFormatTest.cpp

  Log Message:
  -----------
  [SSAF] Add EntitySourceLocationsSummary and JSON format (#208841)

Adds a per-entity TU-level summary recording the canonical (file, line,
column) of each declaration registered against an entity. The data feeds
a follow-on whole-program analysis that groups entities sharing a
declaration source-location into equivalence classes.

Assisted-By: Claude Opus 4.7


  Commit: d9f6dbca81714fd5ee1c5aaf656fed6b0b5a4c01
      https://github.com/llvm/llvm-project/commit/d9f6dbca81714fd5ee1c5aaf656fed6b0b5a4c01
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M libcxx/utils/compare-benchmarks
    M libcxx/utils/requirements.txt

  Log Message:
  -----------
  [libc++] Compute a confidence interval in compare-benchmarks (#208090)

When comparing benchmark results with more than one sample per
benchmark, compute a confidence interval and flag rows that are
statistically significant. This should make the A/B comparison PR job
more robust to noise and easier to rely on. After this change, output
for a multi-sample run looks like:

```
Benchmark                         Baseline    Candidate    Difference    % Difference   Significant?   95% C.I. of %diff
------------------------------  ----------  -----------  ------------  --------------  --------------  -------------------
std::any_of(list<int>)/32            39.92        39.22         -0.70          -1.75%                  [-6.5%, +1.6%]
std::any_of(list<int>)/32768      54071.34     65395.51      11324.17          20.94%                  [-2.8%, +34.5%]
std::any_of(list<int>)/50            67.39        69.08          1.69           2.51%        x         [+0.2%, +4.7%]
std::any_of(list<int>)/8              7.21         6.46         -0.75         -10.40%        x         [-25.0%, -0.7%]
std::any_of(list<int>)/8192       21745.58     22299.32        553.74           2.55%                  [-20.3%, +38.4%]
std::any_of(vector<int>)/32          24.21        14.61         -9.60         -39.65%        x         [-41.2%, -38.4%]
std::any_of(vector<int>)/32768    24365.14     12498.21     -11866.93         -48.70%        x         [-48.9%, -48.6%]
Geomean                             324.15       247.83        -76.32         -23.54%
```

The confidence interval is computed based on the mean of the N samples,
but we still present the median of N in the results. Because of that,
the result is not centered within the confidence interval, and we must
report it as [low, high] instead of a single number. The general idea is
that if 0% falls within the confidence interval, we can't really be
certain that the result changed at all. Similarly, if significant
negative and positive % diffs are in the confidence interval, we can't
be confident that we are introducing an optimization, regression, or any
change at all.

I think this approach is reasonable given the small number of samples
(usually around 3), which severely limits the statistical methods
available to us.

Assisted by Claude


  Commit: 3eb929be5e17d66900020bd1caa7d2510d4f9601
      https://github.com/llvm/llvm-project/commit/3eb929be5e17d66900020bd1caa7d2510d4f9601
  Author: Eli Friedman <efriedma at qti.qualcomm.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M libcxx/src/ios.cpp

  Log Message:
  -----------
  Make ios_base::xalloc non-atomic with LIBCXX_ENABLE_THREADS=OFF. (#208356)

762b77a moved the definition of "xindex" out of the header, and in the
process dropped the _LIBCPP_HAS_THREADS check. Re-add the check to
maintain the status quo.

The discussion on https://github.com/llvm/llvm-project/pull/198994
indicates it's not clear whether LIBCXX_ENABLE_THREADS=OFF is actually
supposed to mean single-threaded. But it clearly does in practice:
atomic_support.h uses non-atomic ops when threads are disabled, and a
few other APIs have explicit non-atomic fallback paths.

My team ran into this trying to run libc++ tests for a RISC-V core
without the "a" extension.


  Commit: 3ae8e355a288a8306bae6cd3ce635ce3de4a1359
      https://github.com/llvm/llvm-project/commit/3ae8e355a288a8306bae6cd3ce635ce3de4a1359
  Author: Lang Hames <lhames at gmail.com>
  Date:   2026-07-15 (Wed, 15 Jul 2026)

  Changed paths:
    M orc-rt/test/unit/CommonTestUtils.h

  Log Message:
  -----------
  [orc-rt] Make noDispatch test helper fail in -Asserts builds. (#209493)

noDispatch guards Sessions that must never dispatch a wrapper call, but
it did so with assert(false), which compiles out under NDEBUG.

Replace the assert with ADD_FAILURE(), which records a failure in every
build mode, and then complete the call via its Return continuation with
an out-of-band error. Completing the call means a caller awaiting the
result unblocks and fails too, rather than hanging, even when the
dispatch arrives on a non-test thread where ADD_FAILURE() alone may not
be observed.


  Commit: 5fc69663ad4a99b8ad0f7cc11e8ba2d626cc2acc
      https://github.com/llvm/llvm-project/commit/5fc69663ad4a99b8ad0f7cc11e8ba2d626cc2acc
  Author: Carlos Seo <carlos.seo at linaro.org>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M flang/lib/Semantics/check-omp-structure.cpp
    M flang/test/Semantics/OpenMP/declare-simd-empty.f90
    A flang/test/Semantics/OpenMP/declare-simd-scope.f90
    M flang/test/Semantics/OpenMP/declare-simd.f90

  Log Message:
  -----------
  [flang][OpenMP] Check the context of the declare_simd directive (#209318)

OpenMP 6.0, 9.8 "declare_simd Directive", restricts the placement of the
directive:

  Any declare_simd directive must appear in the specification part of a
  subroutine subprogram, function subprogram, or interface body to which
  it applies.

Flang did not enforce this, and accepted the directive in the
specification part of a module, submodule, main program or block data.

Note: the restriction requiring the argument to name the procedure to
which the directive applies is not implemented here.

Fixes #205478


  Commit: 71db296bc0f847220e41bd913b6cce4031a23492
      https://github.com/llvm/llvm-project/commit/71db296bc0f847220e41bd913b6cce4031a23492
  Author: qyingwu <46992476+qyingwu at users.noreply.github.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M mlir/lib/Dialect/SparseTensor/Transforms/SparseIterationToScf.cpp
    M mlir/test/Dialect/SparseTensor/sparse_iteration_to_scf.mlir

  Log Message:
  -----------
  [mlir][sparse] Handle dense iterators in sparse iteration lowering (#208963)

Fixes #205980.

`lower-sparse-iteration-to-scf` always called `linkNewScope()` when
lowering
iterators handled by `scf.for`. Dense levels are random-access
iterators, and
`linkNewScope()` asserts for random-access iterators because those
should be
  traversed by coordinate.

Use `locate()` for random-access iterators and keep `linkNewScope()` for
  non-random-access iterators.

  Verification:
  - `cmake --build /tmp/mlir-208198 --target mlir-opt`
- `/tmp/mlir-208198/bin/mlir-opt -lower-sparse-iteration-to-scf
/tmp/issue-
  205980.mlir`
  - `/tmp/mlir-208198/bin/llvm-lit -sv mlir/test/Dialect/SparseTensor/
  sparse_iteration_to_scf.mlir mlir/test/Dialect/SparseTensor/
  sparse_kernels_to_iterator.mlir mlir/test/Dialect/SparseTensor/
  sparse_space_collapse.mlir`


  Commit: 2e38be8333fcd9c17eb7be1b2553b85e0cd9ab15
      https://github.com/llvm/llvm-project/commit/2e38be8333fcd9c17eb7be1b2553b85e0cd9ab15
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M lldb/source/Expression/DWARFExpression.cpp
    M lldb/source/Target/RegisterContextUnwind.cpp

  Log Message:
  -----------
  [lldb] Allow generic operands in DWARF binary type check (#209641)

fc298ccbc52a's CheckScalarOperandsHaveSameType also rejects legitimate
generic-typed operands, breaking breakpad STACK WIN / raSearch unwinding
on 32-bit targets. For `DW_OP_breg7 +0, DW_OP_consts +80, DW_OP_plus`,
DW_OP_breg yields a register-sized (8-byte) scalar while DW_OP_const*
yields an address-sized (4-byte) generic one. The strict size gate ran
before the genericness escape, and the escape only checked the left
operand, so the CFA expression was rejected and the unwind failed.

Reorder so two integers that are each at least as wide as the generic
type are accepted before the size/signedness gate. The commit's own
type-check unit tests still pass.

Also fix a latent crash the failure exposed: ReadFrameAddress and
GetReturnAddressHint only consumed the error inside an UNWIND_LOG
argument, which is skipped when the log is off, so the errored Expected
was destroyed unchecked and aborted. Consume it via LLDB_LOG_ERROR /
LLDB_LOG_ERRORV instead.


  Commit: 4d0a3021c01e15c473e6a515dc8498fb190e3709
      https://github.com/llvm/llvm-project/commit/4d0a3021c01e15c473e6a515dc8498fb190e3709
  Author: Alex MacLean <amaclean at nvidia.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M llvm/lib/Target/NVPTX/CMakeLists.txt
    M llvm/lib/Target/NVPTX/NVPTX.h
    M llvm/lib/Target/NVPTX/NVPTXAsmPrinter.cpp
    M llvm/lib/Target/NVPTX/NVPTXISelLowering.cpp
    M llvm/lib/Target/NVPTX/NVPTXPassRegistry.def
    A llvm/lib/Target/NVPTX/NVPTXPromoteParamAlign.cpp
    R llvm/lib/Target/NVPTX/NVPTXSetByValParamAlign.cpp
    M llvm/lib/Target/NVPTX/NVPTXTargetMachine.cpp
    M llvm/lib/Target/NVPTX/NVPTXUtilities.cpp
    M llvm/lib/Target/NVPTX/NVPTXUtilities.h
    A llvm/test/CodeGen/NVPTX/promote-param-align.ll
    R llvm/test/CodeGen/NVPTX/set-byval-param-align.ll
    M llvm/utils/gn/secondary/llvm/lib/Target/NVPTX/BUILD.gn

  Log Message:
  -----------
  [NVPTX] Promote internal function alignments in IR pass (#208040)

During lowering NVPTX will update the alignment of parameters and return
values if the function is internal and has only compatible direct calls.
Previously this happened within the alignment helper functions during
ISel and assembly printing making it opaque and unreliable. This change
moves that logic to an IR pass so that it can be inspected and disabled
more easily.


  Commit: 68f74b7c1f648f7272f46af5d3d6e314e85601fc
      https://github.com/llvm/llvm-project/commit/68f74b7c1f648f7272f46af5d3d6e314e85601fc
  Author: Florian Mayer <fmayer at google.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M llvm/utils/TableGen/Common/CodeGenDAGPatterns.cpp

  Log Message:
  -----------
  [NFC] [TableGen] mention `srcvalue` in unused input error (#209633)


  Commit: e2fe51e408e097237a214f82385adf97090b3dee
      https://github.com/llvm/llvm-project/commit/e2fe51e408e097237a214f82385adf97090b3dee
  Author: David Young <davidayoung at meta.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M utils/bazel/llvm-project-overlay/lldb/source/Plugins/BUILD.bazel
    M utils/bazel/llvm-project-overlay/lldb/source/Plugins/plugin_config.bzl

  Log Message:
  -----------
  [lldb][bazel] Add ScriptedFrameProvider plugin to the Bazel overlay (#209634)

Adds the PluginScriptedFrameProvider cc_library for the new
SyntheticFrameProvider/ScriptedFrameProvider category and registers it
in DEFAULT_PLUGINS. Deps mirror the plugin's CMakeLists.txt (lldbCore,
lldbInterpreter, lldbTarget, lldbUtility, Support) plus the
:PluginScriptedProcess plugin dep it uses.

The ScriptedFrameProvider plugin was added upstream in PR #161870
("[lldb] Introduce ScriptedFrameProvider for real threads"), relanded as
PR #170236; this wires it into the Bazel overlay build.

bazel rule creation assisted with: claude

Can confirm this rule translates into a valid buck2 rule for Meta to
build internally, but no bazel build locally; will await CI testing.


  Commit: 75fd1ca48059b26360dc961651ec9a23dccff53c
      https://github.com/llvm/llvm-project/commit/75fd1ca48059b26360dc961651ec9a23dccff53c
  Author: Marco Elver <elver at google.com>
  Date:   2026-07-15 (Wed, 15 Jul 2026)

  Changed paths:
    M clang/lib/Analysis/ThreadSafety.cpp
    M clang/test/SemaCXX/warn-thread-safety-analysis.cpp

  Log Message:
  -----------
  Thread Safety Analysis: Handle statement expressions in try-lock conditions (#209330)

Previously, statement expressions (`({ bool b = mu.TryLock(); b; })`)
used as try-lock conditions were not supported. Handle StmtExpr in
getTrylockCallExpr() by recursively analyzing the last statement of the
statement expression.


  Commit: 514b75bbc54f751abdcd32f118f620c3dd2ce4ae
      https://github.com/llvm/llvm-project/commit/514b75bbc54f751abdcd32f118f620c3dd2ce4ae
  Author: Med Ismail Bennani <ismail at bennani.ma>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M lldb/include/lldb/Core/PluginManager.h
    M lldb/include/lldb/Interpreter/CommandCompletions.h
    M lldb/include/lldb/Interpreter/CommandOptionArgumentTable.h
    M lldb/include/lldb/Interpreter/Interfaces/ScriptedInterfaceUsages.h
    M lldb/include/lldb/Interpreter/ScriptInterpreter.h
    M lldb/include/lldb/lldb-enumerations.h
    M lldb/source/Commands/CommandCompletions.cpp
    M lldb/source/Commands/CommandObjectScripting.cpp
    M lldb/source/Commands/Options.td
    M lldb/source/Core/PluginManager.cpp
    M lldb/source/Interpreter/Interfaces/ScriptedInterfaceUsages.cpp
    M lldb/source/Interpreter/ScriptInterpreter.cpp
    A lldb/test/API/commands/scripting/extension/TestScriptingExtensionListJSON.py
    M lldb/test/Shell/Commands/command-scripting-extension-list.test

  Log Message:
  -----------
  [lldb/script] Improve `scripting extension list` output and filtering (#209400)

This patch improves `scripting extension list` in three ways.

First, it groups the output by `ScriptedExtension`: instead of one row
per registered plugin instance, one entry per extension is printed with
a combined `Language` field.

Second, it colorizes and visually separates the output. Each entry is
preceded by a dimmed dashed separator; field labels are printed in bold
green, the extension name value in bold cyan as a mini-heading, and
`None` usage values are dimmed, all via the same
`ansi::FormatAnsiTerminalCodes(..., use_color)` idiom
`Breakpoint::GetDescription` uses elsewhere, gracefully no-op when color
is disabled or unsupported. `ScriptedInterfaceUsages::Dump` takes an
optional `use_color` parameter so its own `API Usages:` / `Command
Interpreter Usages:` labels can match.

Third, it adds `-j`/`--json` to emit a JSON array of `{name,
description, languages, api_usages, command_interpreter_usages}` per
extension, mirroring `plugin list`'s existing `-j`. `DoExecute` now
computes the extension grouping once and branches into
`OutputJsonFormat` or `OutputTextFormat`, sharing a
`GetLanguagesForExtension` helper. It also accepts optional positional
`<extension-name>` arguments to filter the listing to specific
extensions (matched via the same case-insensitive
`ScriptInterpreter::StringToExtension` used by `scripting extension
generate`), with completion wired up via `eScriptedExtensionCompletion`.

Also fix a latent lifetime bug in the shared language-collection helper
so it owns its `std::string` values instead of holding `StringRef`s to
temporaries; the JSON path made it observable.

Signed-off-by: Med Ismail Bennani <ismail at bennani.ma>


  Commit: ef81c51cddcb7395a94da0240ec48e367a60f18c
      https://github.com/llvm/llvm-project/commit/ef81c51cddcb7395a94da0240ec48e367a60f18c
  Author: Endre Fülöp <endre.fulop at sigmatechnology.com>
  Date:   2026-07-15 (Wed, 15 Jul 2026)

  Changed paths:
    M clang/docs/ReleaseNotes.md
    M clang/docs/analyzer/checkers.rst
    M clang/include/clang/StaticAnalyzer/Checkers/Checkers.td
    M clang/lib/StaticAnalyzer/Checkers/PthreadLockChecker.cpp
    M clang/test/Analysis/analyzer-config.c
    M clang/test/Analysis/c11lock.c
    M clang/test/Analysis/fuchsia_lock.c
    M clang/test/Analysis/pthreadlock-notes.c
    M clang/test/Analysis/pthreadlock.c

  Log Message:
  -----------
  [analyzer] Disable lock order reversal check by default in PthreadLoc… (#202452)

…kChecker

Lock order reversal is a real source of deadlocks, but the current
single-path intraprocedural analysis is a single-path analysis, and it
cannot reason about potentially overlapping executions.This makes this
part of the checker too imprecise for default-on.

Add a WarnOnLockOrderReversal option (default: false) for the previous
behavior.


  Commit: 4a223ced16f7aec0389b4b6257a8aecfe5cf57bf
      https://github.com/llvm/llvm-project/commit/4a223ced16f7aec0389b4b6257a8aecfe5cf57bf
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M lldb/source/Expression/DWARFExpression.cpp

  Log Message:
  -----------
  [lldb] Distinguish DWARF binary type-check error messages (#209644)

CheckScalarOperandsHaveSameType reported every operand-check failure
with the same "requires operands to have the same type" message, even
though it rejects operands for three different reasons: mismatched type
kind, mismatched size, and mismatched signedness. That made a failed
check hard to diagnose from the error alone.

Parameterize the message so each check names what actually differs
(type, size, or signedness).

Follow-up to Augusto's review of #209641.


  Commit: 23040e8b2f9256cf4fba5af30a10593cb691f39d
      https://github.com/llvm/llvm-project/commit/23040e8b2f9256cf4fba5af30a10593cb691f39d
  Author: Thurston Dang <thurston at google.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    A llvm/test/Instrumentation/MemorySanitizer/X86/avx512dq-intrinsics.ll

  Log Message:
  -----------
  [msan][NFCI] Add AVX512 DQ tests (#207059)

This adds tests for AVX512 DQ ("Doubleword and Quadword Instructions",
not to be mistaken with Dairy Queen), forked from
llvm/test/CodeGen/X86/avx512dq-intrinsics.ll.


  Commit: d7e6268cf237308ff84fc1afbb5638862d5cac3f
      https://github.com/llvm/llvm-project/commit/d7e6268cf237308ff84fc1afbb5638862d5cac3f
  Author: Thurston Dang <thurston at google.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M llvm/lib/Transforms/Instrumentation/MemorySanitizer.cpp

  Log Message:
  -----------
  [msan][NFCI] Add forceIntegerIntrinsic option to handleIntrinsicByApplyingToShadow() (#207053)

Currently, if handleIntrinsicByApplyingToShadow() is given an
IntrinsicInst with floating-point arguments, it will cast the shadows to
floating-point, apply the intrinsic, and then cast the result back to
integer/shadow. This is inefficient, and, depending on the intrinsic,
may also result in floating-point exceptions.

The user can explicitly supply an integer variant of the intrinsic to be
applied to the shadow (shadowIntrinsicID), but this does not work if the
integer and floating-point variants are overloaded forms of the same
intrinsic ID.

This patch adds an option, 'forceIntegerIntrinsic', which will pass the
shadows as integers to the intrinsic, thus avoiding unnecessary casts.
(This is not enabled by default since some intrinsics do not support
integer arguments.)

As an example, future work can use 'forceIntegerIntrinsic' to handle
`<16 x float> @llvm.x86.avx512.mask.compress (<16 x float>, <16 x
float>, <16 x i1> %mask)`
with
`<16 x i32> @llvm.x86.avx512.mask.compress (<16 x i32>, <16 x i32>, <16
x i1> %mask)`


  Commit: 3f58d3dfe808a5605c72fa812776ed6495188a6b
      https://github.com/llvm/llvm-project/commit/3f58d3dfe808a5605c72fa812776ed6495188a6b
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M lldb/test/API/functionalities/statusline/TestStatusline.py
    M lldb/test/API/functionalities/statusline/statusline_flood.py

  Log Message:
  -----------
  [lldb][test] Deflake the statusline scripted-command output test (#209643)

test_scripted_command_output_not_eaten failed intermittently in CI on
its assertIn(b"\x1b7", data) guard because the captured window held no
statusline escape at all, only the command output and the next prompt.

The cause is a thread-scheduling race, not a bug. The statusline is
redrawn on the event thread once per progress event, but on a loaded
machine the event thread need not run until the flood command has
already returned, so it drains the queued progress events after (lldb)
was matched and the capture stopped, leaving no redraw to inspect.

Widen the flood (the line count is now an argument) so the event thread
has a larger window to redraw in, and retry until at least one complete
cursor save/restore pair is observed before checking that no output was
spliced into it. If a redraw is never seen, skip rather than fail.

I deliberately avoided a per-line sleep as it would let each redraw
finish between prints and hide the very interleaving the test looks for.

Fixes #209605


  Commit: 5be3fdbc59fd78d0b86236ebc44c10c41571ce4c
      https://github.com/llvm/llvm-project/commit/5be3fdbc59fd78d0b86236ebc44c10c41571ce4c
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M lldb/include/lldb/Host/Editline.h
    M lldb/source/Host/common/Editline.cpp

  Log Message:
  -----------
  [lldb] Use std::atomic<bool> for Editline's pending-resize flag (#209619)

TerminalSizeChanged() used a volatile std::sig_atomic_t to record that a
resize is pending. That type was chosen because the SIGWINCH handler ran
in async-signal context and could only touch an sig_atomic_t. Signals
are now handled on a dedicated thread, so the flag is written from a
normal thread and std::atomic<bool> is sufficient to handle that.

el_resize() still runs on the thread that owns libedit, in its read
loop. I discovered that it is not safe to run elsewhere, because it
resets libedit's display model without redrawing. Applying it off that
thread seems to throw it off and makes it duplicate the prompt.


  Commit: 6dc5473fa6846830134f3ffe2257113382200391
      https://github.com/llvm/llvm-project/commit/6dc5473fa6846830134f3ffe2257113382200391
  Author: Rafael Auler <rafaelauler at meta.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M bolt/include/bolt/Core/BinaryContext.h
    M bolt/include/bolt/Core/BinaryFunction.h
    M bolt/lib/Core/BinaryContext.cpp
    M bolt/lib/Core/BinaryEmitter.cpp
    M bolt/lib/Core/BinaryFunction.cpp
    M bolt/lib/Rewrite/RewriteInstance.cpp
    A bolt/test/X86/dwarf-inline-range-plt-shift.s

  Log Message:
  -----------
  [BOLT] Fix shifted DWARF inline-scope ranges; track scope boundaries (#207291)

Summary:
BOLT updated DWARF lexical-scope ranges (DW_TAG_inlined_subroutine /
lexical_block low_pc/high_pc and DW_AT_ranges) via
translateInputToOutputRange(), which mapped a boundary using its input
offset relative to the start of the containing basic block:

OutAddr = BB.getOutputAddressRange().first + (InputOffset -
BB.getOffset())

This assumes intra-block byte offsets are preserved input->output. Any
pass that changes instruction sizes within a block ahead of a scope
boundary breaks that assumption. With --plt=all, each `call foo at PLT` (5
bytes, e8+rel32) is rewritten to `call *foo at GOT(%rip)` (6 bytes, ff
15+rel32); N such calls before a boundary shift its emitted low_pc/
high_pc N bytes too early, onto the preceding instruction. The range
stays within the parent so `llvm-dwarfdump --verify` does not catch it;
symbolizers then attribute samples on those instructions to the wrong
inlined frames.

Fix is to resolve scope-range boundaries through the precise
per-instruction input-to-output AddressMap (the same map BAT already
uses) instead of input-relative block offsets. Boundary instructions are
arbitrary (not just calls/branches), so they are normally absent from
that map; to make them resolvable, disassembly now keeps an offset for
the boundary instructions (only the boundaries, to keep the AddressMap
small) and those offsets are emitted as AddressMap entries whenever an
address map is required (requiresAddressMap(), which includes
--update-debug-sections via requiresPreciseAddressMap()), not only under
BAT.

Boundary collection (BinaryContext::collectDebugScopeBoundaries) runs in
readDebugInfo() after preprocessDebugInfo(). It streams the DIEs of the
CUs that will be updated directly from the already-loaded DWARFContext
with DWARFDebugInfoEntry::extractFast, decoding one DIE at a time into a
single reusable entry, so no DIE forest is materialized and no second
DWARF context is created. For split DWARF the .dwo DIEs are already
extracted by preprocessDWODebugInfo(), so the cached array is reused
instead. Boundaries are stored per function in a sorted, deduplicated
vector (BinaryFunction::DebugScopeBoundaryOffsets), queried during
disassembly with a monotonic cursor, and freed once the function is
disassembled, so the feature adds no global state.

The behavior is on by default and can be disabled with
--accurate-debug-ranges=0, which falls back to the old block-relative
mapping.

Test on big binaries with split dwarf, -lite=0:
                                wall                Max RSS
      -accurate-debug-ranges=0  1070.1s             94.91
      -accurate-debug-ranges=1  1173.0s             100.07
      delta                     +102.9s             +5.16   (+4.6% CPU,
                                                             +5.4% RSS)

Test on big binaries with split dwarf, lite=1:
      -accurate-debug-ranges=0  433.9s              83.23
      -accurate-debug-ranges=1  434.7s              83.79   (+0.7% RSS)

    --time-rewrite shows the boundary-collection phase itself is cheap:
    "read debug ranges" is 5.8s of 4960s total user time on one binary
    (0.1%) and 18.8s of 6307s on another binary; the feature's
cost is dominated by emitting/translating the extra AddressMap entries,
    not by collection.


  Commit: e2ead479f043a10e9b6d74f633346b96f37d9b2b
      https://github.com/llvm/llvm-project/commit/e2ead479f043a10e9b6d74f633346b96f37d9b2b
  Author: Sam Elliott <aelliott at qti.qualcomm.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M llvm/test/MC/RISCV/xqcia-invalid.s
    M llvm/test/MC/RISCV/xqciac-invalid.s
    M llvm/test/MC/RISCV/xqcibi-invalid.s
    M llvm/test/MC/RISCV/xqcibm-invalid.s
    M llvm/test/MC/RISCV/xqcicli-invalid.s
    M llvm/test/MC/RISCV/xqcicm-invalid.s
    M llvm/test/MC/RISCV/xqcics-invalid.s
    M llvm/test/MC/RISCV/xqcicsr-invalid.s
    M llvm/test/MC/RISCV/xqciint-invalid.s
    M llvm/test/MC/RISCV/xqcilb-invalid.s
    M llvm/test/MC/RISCV/xqcili-invalid.s
    M llvm/test/MC/RISCV/xqcilia-invalid.s
    M llvm/test/MC/RISCV/xqcilo-invalid.s
    M llvm/test/MC/RISCV/xqcilsm-invalid.s
    M llvm/test/MC/RISCV/xqcisim-invalid.s
    M llvm/test/MC/RISCV/xqcisls-invalid.s
    M llvm/test/MC/RISCV/xqcisync-invalid.s

  Log Message:
  -----------
  [RISCV][MC][NFC] Cleanup Xqci Tests (#209646)


  Commit: a6d35f4715f1b6aaf1339bfa63e92685c0f46ed2
      https://github.com/llvm/llvm-project/commit/a6d35f4715f1b6aaf1339bfa63e92685c0f46ed2
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M lldb/source/Plugins/Protocol/MCP/ProtocolServerMCP.cpp
    M lldb/source/Plugins/Protocol/MCP/ProtocolServerMCP.h
    M lldb/source/Plugins/Protocol/MCP/Tool.cpp
    M lldb/source/Plugins/Protocol/MCP/Tool.h
    M lldb/unittests/Protocol/MCPPluginTest.cpp

  Log Message:
  -----------
  [lldb] Add MCP tools to create and destroy debugger instances (#209288)

Add debugger_create and debugger_delete tools to the MCP server so a
client can manage debugger instances, not just command the ones that
already exist. debugger_create detaches the new debugger's stdio from
the host process (redirecting input/output/error to the null device) so
its prompt and asynchronous output cannot corrupt an MCP stream that
shares the host's stdout. Command results flow through
CommandReturnObject and are unaffected.

Factor the tool and resource registration out of
ProtocolServerMCP::Extend into a shared PopulateServer() so an embedded
in-process server (e.g. in lldb-mcp) can install the same set.

Assisted-by: Claude

rdar://181722721


  Commit: f7491eae219f3f5fb5d6ebd187977fb3f9eaa89a
      https://github.com/llvm/llvm-project/commit/f7491eae219f3f5fb5d6ebd187977fb3f9eaa89a
  Author: Thurston Dang <thurston at google.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M llvm/lib/Transforms/Utils/MetaRenamer.cpp
    M llvm/test/Transforms/MetaRenamer/metarenamer.ll
    M llvm/test/Transforms/MetaRenamer/opcodes.ll

  Log Message:
  -----------
  [MetaRenamer] Change basic block naming from 'bb' to 'bbl' (#205393)

Currently, `update_test_checks.py` warns when run on MetaRenamer output
e.g., `WARNING: Change IR value name 'bb3' or use
--prefix-filecheck-ir-name to prevent possible conflict with scripted
FileCheck name.`

Avoid this conflict by changing MetaRenamer to use 'bbl' for basic
blocks.

This is similar in spirit to

https://github.com/llvm/llvm-project/commit/86a63b2ae147e5a3edc39643783acfd39b059c92,
which renamed instructions from 'tmp' to 'inst' to avoid a conflict with
automatically-generated checks.


  Commit: f89a59461103fdf71bd6c69dd68476b0e568fa52
      https://github.com/llvm/llvm-project/commit/f89a59461103fdf71bd6c69dd68476b0e568fa52
  Author: Andy Kaylor <akaylor at nvidia.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M clang/test/CIR/CodeGenBuiltins/X86/avx10_2_512bf16-builtins.c
    M clang/test/CIR/CodeGenBuiltins/X86/avx10_2bf16-builtins.c
    M clang/test/CIR/CodeGenBuiltins/X86/keylocker.c

  Log Message:
  -----------
  [CIR] Fix x86 builtin tests after tighter inlining (#209653)

The behavior of the AlwaysInliner was tightened in a recent change
(https://github.com/llvm/llvm-project/pull/209345) to avoid inling
functions with mismatched target attributes even when the alwaysinline
attribute was present. This exposed a few failures in CIR where we were
either running with stale target features or missing target features
that were needed for the builtins we were testing.

This change updates the run lines to use the correct feature sets.


  Commit: 6ce9488de626f6e791f1d6cdce2562842f665944
      https://github.com/llvm/llvm-project/commit/6ce9488de626f6e791f1d6cdce2562842f665944
  Author: Aiden Grossman <aidengrossman at google.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M llvm/utils/lit/tests/Inputs/per-test-coverage-by-lit-cfg/lit.cfg
    M llvm/utils/lit/tests/Inputs/per-test-coverage/lit.cfg
    R llvm/utils/lit/tests/Inputs/shtest-external-shell-kill/lit.cfg
    R llvm/utils/lit/tests/Inputs/shtest-external-shell-kill/test.txt
    M llvm/utils/lit/tests/Inputs/shtest-readfile/lit.cfg
    A llvm/utils/lit/tests/Inputs/shtest-run-at-line/basic.txt
    A llvm/utils/lit/tests/Inputs/shtest-run-at-line/empty-run-line.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/external-shell/basic.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/external-shell/empty-run-line.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/external-shell/line-continuation.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/external-shell/lit.local.cfg
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/external-shell/run-line-with-newline.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/internal-shell/basic.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/internal-shell/empty-run-line.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/internal-shell/line-continuation.txt
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/internal-shell/lit.local.cfg
    R llvm/utils/lit/tests/Inputs/shtest-run-at-line/internal-shell/run-line-with-newline.txt
    A llvm/utils/lit/tests/Inputs/shtest-run-at-line/line-continuation.txt
    M llvm/utils/lit/tests/Inputs/shtest-run-at-line/lit.cfg
    A llvm/utils/lit/tests/Inputs/shtest-run-at-line/run-line-with-newline.txt
    M llvm/utils/lit/tests/Inputs/shtest-timeout/lit.cfg
    M llvm/utils/lit/tests/per-test-coverage-by-lit-cfg.py
    M llvm/utils/lit/tests/per-test-coverage.py
    R llvm/utils/lit/tests/shtest-external-shell-kill.py
    R llvm/utils/lit/tests/shtest-readfile-external.py
    M llvm/utils/lit/tests/shtest-run-at-line.py
    M llvm/utils/lit/tests/shtest-timeout.py

  Log Message:
  -----------
  [lit] Remove most external shell test coverage

Now that LLVM 23 has branched, we can look at removing the external
shell.

https://discourse.llvm.org/t/rfc-removal-of-the-lit-external-shell/90951

This patch removes most test coverage that was explicitly for the
external shell as it was entirely duplicated with the internal shell.
This patch leaves out removing test coverage in shtest-format as not all
the coverage there is duplicated and it seems like there is some missing
from the internal shell and I want to give it more careful
consideration.

Reviewers: hnrklssn, ilovepi, jh7370, arichardson

Pull Request: https://github.com/llvm/llvm-project/pull/209500


  Commit: e82736dd69e611f898d61aac55045b317f3e3db8
      https://github.com/llvm/llvm-project/commit/e82736dd69e611f898d61aac55045b317f3e3db8
  Author: Aiden Grossman <aidengrossman at google.com>
  Date:   2026-07-15 (Wed, 15 Jul 2026)

  Changed paths:
    M bolt/include/bolt/Core/BinaryContext.h
    M bolt/include/bolt/Core/BinaryFunction.h
    M bolt/lib/Core/BinaryContext.cpp
    M bolt/lib/Core/BinaryEmitter.cpp
    M bolt/lib/Core/BinaryFunction.cpp
    M bolt/lib/Rewrite/RewriteInstance.cpp
    A bolt/test/X86/dwarf-inline-range-plt-shift.s
    M clang/docs/ReleaseNotes.md
    M clang/docs/analyzer/checkers.rst
    A clang/include/clang/ScalableStaticAnalysis/Analyses/SharedLexicalRepresentation/SharedLexicalRepresentation.h
    M clang/include/clang/ScalableStaticAnalysis/BuiltinAnchorSources.def
    M clang/include/clang/StaticAnalyzer/Checkers/Checkers.td
    M clang/lib/Analysis/ThreadSafety.cpp
    M clang/lib/ScalableStaticAnalysis/Analyses/CMakeLists.txt
    A clang/lib/ScalableStaticAnalysis/Analyses/SharedLexicalRepresentation/SharedLexicalRepresentationFormat.cpp
    M clang/lib/StaticAnalyzer/Checkers/PthreadLockChecker.cpp
    M clang/test/Analysis/analyzer-config.c
    M clang/test/Analysis/c11lock.c
    M clang/test/Analysis/fuchsia_lock.c
    M clang/test/Analysis/pthreadlock-notes.c
    M clang/test/Analysis/pthreadlock.c
    M clang/test/CIR/CodeGenBuiltins/X86/avx10_2_512bf16-builtins.c
    M clang/test/CIR/CodeGenBuiltins/X86/avx10_2bf16-builtins.c
    M clang/test/CIR/CodeGenBuiltins/X86/keylocker.c
    M clang/test/SemaCXX/warn-thread-safety-analysis.cpp
    M clang/unittests/ScalableStaticAnalysis/CMakeLists.txt
    A clang/unittests/ScalableStaticAnalysis/Serialization/JSONFormatTest/SharedLexicalRepresentationFormatTest.cpp
    M flang/lib/Semantics/check-omp-structure.cpp
    M flang/test/Semantics/OpenMP/declare-simd-empty.f90
    A flang/test/Semantics/OpenMP/declare-simd-scope.f90
    M flang/test/Semantics/OpenMP/declare-simd.f90
    M libcxx/src/ios.cpp
    M libcxx/utils/compare-benchmarks
    M libcxx/utils/requirements.txt
    M lldb/include/lldb/Core/PluginManager.h
    M lldb/include/lldb/Host/Editline.h
    M lldb/include/lldb/Interpreter/CommandCompletions.h
    M lldb/include/lldb/Interpreter/CommandOptionArgumentTable.h
    M lldb/include/lldb/Interpreter/Interfaces/ScriptedInterfaceUsages.h
    M lldb/include/lldb/Interpreter/ScriptInterpreter.h
    M lldb/include/lldb/lldb-enumerations.h
    M lldb/source/Commands/CommandCompletions.cpp
    M lldb/source/Commands/CommandObjectScripting.cpp
    M lldb/source/Commands/Options.td
    M lldb/source/Core/PluginManager.cpp
    M lldb/source/Expression/DWARFExpression.cpp
    M lldb/source/Host/common/Editline.cpp
    M lldb/source/Interpreter/Interfaces/ScriptedInterfaceUsages.cpp
    M lldb/source/Interpreter/ScriptInterpreter.cpp
    M lldb/source/Plugins/Protocol/MCP/ProtocolServerMCP.cpp
    M lldb/source/Plugins/Protocol/MCP/ProtocolServerMCP.h
    M lldb/source/Plugins/Protocol/MCP/Tool.cpp
    M lldb/source/Plugins/Protocol/MCP/Tool.h
    M lldb/source/Target/RegisterContextUnwind.cpp
    A lldb/test/API/commands/scripting/extension/TestScriptingExtensionListJSON.py
    M lldb/test/API/functionalities/statusline/TestStatusline.py
    M lldb/test/API/functionalities/statusline/statusline_flood.py
    M lldb/test/API/tools/lldb-dap/stackTrace/TestDAP_stackTrace.py
    M lldb/test/Shell/Commands/command-scripting-extension-list.test
    M lldb/unittests/Protocol/MCPPluginTest.cpp
    M llvm/lib/Target/NVPTX/CMakeLists.txt
    M llvm/lib/Target/NVPTX/NVPTX.h
    M llvm/lib/Target/NVPTX/NVPTXAsmPrinter.cpp
    M llvm/lib/Target/NVPTX/NVPTXISelLowering.cpp
    M llvm/lib/Target/NVPTX/NVPTXPassRegistry.def
    A llvm/lib/Target/NVPTX/NVPTXPromoteParamAlign.cpp
    R llvm/lib/Target/NVPTX/NVPTXSetByValParamAlign.cpp
    M llvm/lib/Target/NVPTX/NVPTXTargetMachine.cpp
    M llvm/lib/Target/NVPTX/NVPTXUtilities.cpp
    M llvm/lib/Target/NVPTX/NVPTXUtilities.h
    M llvm/lib/Transforms/Instrumentation/MemorySanitizer.cpp
    M llvm/lib/Transforms/Utils/MetaRenamer.cpp
    A llvm/test/CodeGen/NVPTX/promote-param-align.ll
    R llvm/test/CodeGen/NVPTX/set-byval-param-align.ll
    A llvm/test/Instrumentation/MemorySanitizer/X86/avx512dq-intrinsics.ll
    M llvm/test/MC/RISCV/xqcia-invalid.s
    M llvm/test/MC/RISCV/xqciac-invalid.s
    M llvm/test/MC/RISCV/xqcibi-invalid.s
    M llvm/test/MC/RISCV/xqcibm-invalid.s
    M llvm/test/MC/RISCV/xqcicli-invalid.s
    M llvm/test/MC/RISCV/xqcicm-invalid.s
    M llvm/test/MC/RISCV/xqcics-invalid.s
    M llvm/test/MC/RISCV/xqcicsr-invalid.s
    M llvm/test/MC/RISCV/xqciint-invalid.s
    M llvm/test/MC/RISCV/xqcilb-invalid.s
    M llvm/test/MC/RISCV/xqcili-invalid.s
    M llvm/test/MC/RISCV/xqcilia-invalid.s
    M llvm/test/MC/RISCV/xqcilo-invalid.s
    M llvm/test/MC/RISCV/xqcilsm-invalid.s
    M llvm/test/MC/RISCV/xqcisim-invalid.s
    M llvm/test/MC/RISCV/xqcisls-invalid.s
    M llvm/test/MC/RISCV/xqcisync-invalid.s
    M llvm/test/Transforms/MetaRenamer/metarenamer.ll
    M llvm/test/Transforms/MetaRenamer/opcodes.ll
    M llvm/utils/TableGen/Common/CodeGenDAGPatterns.cpp
    M llvm/utils/gn/secondary/llvm/lib/Target/NVPTX/BUILD.gn
    M mlir/lib/Dialect/SparseTensor/Transforms/SparseIterationToScf.cpp
    M mlir/test/Dialect/SparseTensor/sparse_iteration_to_scf.mlir
    M orc-rt/test/unit/CommonTestUtils.h
    M utils/bazel/llvm-project-overlay/lldb/source/Plugins/BUILD.bazel
    M utils/bazel/llvm-project-overlay/lldb/source/Plugins/plugin_config.bzl

  Log Message:
  -----------
  [𝘀𝗽𝗿] changes introduced through rebase

Created using spr 1.3.7

[skip ci]


  Commit: 2778658c3b40e466bbcac8017758f43858d85aac
      https://github.com/llvm/llvm-project/commit/2778658c3b40e466bbcac8017758f43858d85aac
  Author: Aiden Grossman <aidengrossman at google.com>
  Date:   2026-07-15 (Wed, 15 Jul 2026)

  Changed paths:
    M bolt/include/bolt/Core/BinaryContext.h
    M bolt/include/bolt/Core/BinaryFunction.h
    M bolt/lib/Core/BinaryContext.cpp
    M bolt/lib/Core/BinaryEmitter.cpp
    M bolt/lib/Core/BinaryFunction.cpp
    M bolt/lib/Rewrite/RewriteInstance.cpp
    A bolt/test/X86/dwarf-inline-range-plt-shift.s
    M clang/docs/ReleaseNotes.md
    M clang/docs/analyzer/checkers.rst
    A clang/include/clang/ScalableStaticAnalysis/Analyses/SharedLexicalRepresentation/SharedLexicalRepresentation.h
    M clang/include/clang/ScalableStaticAnalysis/BuiltinAnchorSources.def
    M clang/include/clang/StaticAnalyzer/Checkers/Checkers.td
    M clang/lib/Analysis/ThreadSafety.cpp
    M clang/lib/ScalableStaticAnalysis/Analyses/CMakeLists.txt
    A clang/lib/ScalableStaticAnalysis/Analyses/SharedLexicalRepresentation/SharedLexicalRepresentationFormat.cpp
    M clang/lib/StaticAnalyzer/Checkers/PthreadLockChecker.cpp
    M clang/test/Analysis/analyzer-config.c
    M clang/test/Analysis/c11lock.c
    M clang/test/Analysis/fuchsia_lock.c
    M clang/test/Analysis/pthreadlock-notes.c
    M clang/test/Analysis/pthreadlock.c
    M clang/test/CIR/CodeGenBuiltins/X86/avx10_2_512bf16-builtins.c
    M clang/test/CIR/CodeGenBuiltins/X86/avx10_2bf16-builtins.c
    M clang/test/CIR/CodeGenBuiltins/X86/keylocker.c
    M clang/test/SemaCXX/warn-thread-safety-analysis.cpp
    M clang/unittests/ScalableStaticAnalysis/CMakeLists.txt
    A clang/unittests/ScalableStaticAnalysis/Serialization/JSONFormatTest/SharedLexicalRepresentationFormatTest.cpp
    M flang/lib/Semantics/check-omp-structure.cpp
    M flang/test/Semantics/OpenMP/declare-simd-empty.f90
    A flang/test/Semantics/OpenMP/declare-simd-scope.f90
    M flang/test/Semantics/OpenMP/declare-simd.f90
    M libcxx/src/ios.cpp
    M libcxx/utils/compare-benchmarks
    M libcxx/utils/requirements.txt
    M lldb/include/lldb/Core/PluginManager.h
    M lldb/include/lldb/Host/Editline.h
    M lldb/include/lldb/Interpreter/CommandCompletions.h
    M lldb/include/lldb/Interpreter/CommandOptionArgumentTable.h
    M lldb/include/lldb/Interpreter/Interfaces/ScriptedInterfaceUsages.h
    M lldb/include/lldb/Interpreter/ScriptInterpreter.h
    M lldb/include/lldb/lldb-enumerations.h
    M lldb/source/Commands/CommandCompletions.cpp
    M lldb/source/Commands/CommandObjectScripting.cpp
    M lldb/source/Commands/Options.td
    M lldb/source/Core/PluginManager.cpp
    M lldb/source/Expression/DWARFExpression.cpp
    M lldb/source/Host/common/Editline.cpp
    M lldb/source/Interpreter/Interfaces/ScriptedInterfaceUsages.cpp
    M lldb/source/Interpreter/ScriptInterpreter.cpp
    M lldb/source/Plugins/Protocol/MCP/ProtocolServerMCP.cpp
    M lldb/source/Plugins/Protocol/MCP/ProtocolServerMCP.h
    M lldb/source/Plugins/Protocol/MCP/Tool.cpp
    M lldb/source/Plugins/Protocol/MCP/Tool.h
    M lldb/source/Target/RegisterContextUnwind.cpp
    A lldb/test/API/commands/scripting/extension/TestScriptingExtensionListJSON.py
    M lldb/test/API/functionalities/statusline/TestStatusline.py
    M lldb/test/API/functionalities/statusline/statusline_flood.py
    M lldb/test/API/tools/lldb-dap/stackTrace/TestDAP_stackTrace.py
    M lldb/test/Shell/Commands/command-scripting-extension-list.test
    M lldb/unittests/Protocol/MCPPluginTest.cpp
    M llvm/lib/Target/NVPTX/CMakeLists.txt
    M llvm/lib/Target/NVPTX/NVPTX.h
    M llvm/lib/Target/NVPTX/NVPTXAsmPrinter.cpp
    M llvm/lib/Target/NVPTX/NVPTXISelLowering.cpp
    M llvm/lib/Target/NVPTX/NVPTXPassRegistry.def
    A llvm/lib/Target/NVPTX/NVPTXPromoteParamAlign.cpp
    R llvm/lib/Target/NVPTX/NVPTXSetByValParamAlign.cpp
    M llvm/lib/Target/NVPTX/NVPTXTargetMachine.cpp
    M llvm/lib/Target/NVPTX/NVPTXUtilities.cpp
    M llvm/lib/Target/NVPTX/NVPTXUtilities.h
    M llvm/lib/Transforms/Instrumentation/MemorySanitizer.cpp
    M llvm/lib/Transforms/Utils/MetaRenamer.cpp
    A llvm/test/CodeGen/NVPTX/promote-param-align.ll
    R llvm/test/CodeGen/NVPTX/set-byval-param-align.ll
    A llvm/test/Instrumentation/MemorySanitizer/X86/avx512dq-intrinsics.ll
    M llvm/test/MC/RISCV/xqcia-invalid.s
    M llvm/test/MC/RISCV/xqciac-invalid.s
    M llvm/test/MC/RISCV/xqcibi-invalid.s
    M llvm/test/MC/RISCV/xqcibm-invalid.s
    M llvm/test/MC/RISCV/xqcicli-invalid.s
    M llvm/test/MC/RISCV/xqcicm-invalid.s
    M llvm/test/MC/RISCV/xqcics-invalid.s
    M llvm/test/MC/RISCV/xqcicsr-invalid.s
    M llvm/test/MC/RISCV/xqciint-invalid.s
    M llvm/test/MC/RISCV/xqcilb-invalid.s
    M llvm/test/MC/RISCV/xqcili-invalid.s
    M llvm/test/MC/RISCV/xqcilia-invalid.s
    M llvm/test/MC/RISCV/xqcilo-invalid.s
    M llvm/test/MC/RISCV/xqcilsm-invalid.s
    M llvm/test/MC/RISCV/xqcisim-invalid.s
    M llvm/test/MC/RISCV/xqcisls-invalid.s
    M llvm/test/MC/RISCV/xqcisync-invalid.s
    M llvm/test/Transforms/MetaRenamer/metarenamer.ll
    M llvm/test/Transforms/MetaRenamer/opcodes.ll
    M llvm/utils/TableGen/Common/CodeGenDAGPatterns.cpp
    M llvm/utils/gn/secondary/llvm/lib/Target/NVPTX/BUILD.gn
    M llvm/utils/lit/tests/shtest-format.py
    M mlir/lib/Dialect/SparseTensor/Transforms/SparseIterationToScf.cpp
    M mlir/test/Dialect/SparseTensor/sparse_iteration_to_scf.mlir
    M orc-rt/test/unit/CommonTestUtils.h
    M utils/bazel/llvm-project-overlay/lldb/source/Plugins/BUILD.bazel
    M utils/bazel/llvm-project-overlay/lldb/source/Plugins/plugin_config.bzl

  Log Message:
  -----------
  feedback

Created using spr 1.3.7


Compare: https://github.com/llvm/llvm-project/compare/c3bea50015ec...2778658c3b40

To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list