[all-commits] [llvm/llvm-project] d1899a: [X86] combineConcatVectorOps - add handling to con...

Mon Dec 1 11:01:01 PST 2025

  Branch: refs/heads/users/rampitec/11-17-_amdgpu_allow_hazard_checks_for_wmma_co-exec
  Home:   https://github.com/llvm/llvm-project
  Commit: d1899acd08d3eb876de0e5394f6c3a2441e04756
      https://github.com/llvm/llvm-project/commit/d1899acd08d3eb876de0e5394f6c3a2441e04756
  Author: Simon Pilgrim <llvm-dev at redking.me.uk>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M llvm/lib/Target/X86/X86ISelLowering.cpp
    M llvm/test/CodeGen/X86/combine-ffloor.ll
    M llvm/test/CodeGen/X86/combine-fround.ll

  Log Message:
  -----------
  [X86] combineConcatVectorOps - add handling to concat ISD::FROUND/FFLOOR intrinsics together (#170176)

These were missed in #170160

  Commit: 21e64d1f5a3dbf539eaf9c7ac160469e60222ba2
      https://github.com/llvm/llvm-project/commit/21e64d1f5a3dbf539eaf9c7ac160469e60222ba2
  Author: Valentin Clement (バレンタイン クレメン) <clementval at gmail.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    A flang/include/flang/Optimizer/Transforms/CUDA/CUFAllocationConversion.h
    M flang/include/flang/Optimizer/Transforms/Passes.td
    M flang/lib/Optimizer/Transforms/CMakeLists.txt
    A flang/lib/Optimizer/Transforms/CUDA/CUFAllocationConversion.cpp
    M flang/lib/Optimizer/Transforms/CUFOpConversion.cpp

  Log Message:
  -----------
  [flang][cuda][NFC] Split allocation related operation conversion from other cuf operations (#169740)

Split AllocOp, FreeOp, AllocateOp and DeallocateOp from other
conversion. Patterns are currently added to the base CUFOpConversion
when the option is enabled.
This split is a pre-requisite to be more flexible where we do the
allocation related operations conversion in the pipeline.

  Commit: c9d9dddc1c5e9f203f5db890f383b956c5b2d295
      https://github.com/llvm/llvm-project/commit/c9d9dddc1c5e9f203f5db890f383b956c5b2d295
  Author: nerix <nerixdev at outlook.de>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M lldb/source/Plugins/SymbolFile/NativePDB/SymbolFileNativePDB.cpp
    A lldb/test/Shell/SymbolFile/NativePDB/find-pdb-next-to-exe.test

  Log Message:
  -----------
  [LLDB][NativePDB] Look for PDBs in `target.debug-file-search-paths` (#169719)

Similar to DWARF's DWO, we should look for PDBs in
`target.debug-file-search-paths` if the PDB isn't at the original
location or next to the executable.

With this PR, the search order is as follows:

1. PDB path specified in the PE/COFF file
2. Next to the executable
3. In `target.debug-file-search-paths`

This roughly matches [the order Visual Studio
uses](https://learn.microsoft.com/en-us/visualstudio/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger?view=vs-2022#where-the-debugger-looks-for-symbols),
except that we don't have a project folder and don't support symbol
servers.

Closes #125355 (though I think this is already fixed in the native
plugin).

  Commit: c103d61758e61a9fe4c1963b29d602ffe2c22427
      https://github.com/llvm/llvm-project/commit/c103d61758e61a9fe4c1963b29d602ffe2c22427
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M lldb/source/Core/Statusline.cpp
    M lldb/test/API/functionalities/statusline/TestStatusline.py

  Log Message:
  -----------
  [lldb] Fix a bug when disabling the statusline. (#169127)

Currently, disabling the statusline with `settings set show-statusline
false` leaves LLDB in a broken state. The same is true when trying to
toggle the setting again.

The issue was that setting the scroll window to 0 is apparently not
identical to setting it to the correct number of rows, even though some
documentation online incorrectly claims so.

Fixes #166608

  Commit: 56d061ccc5afb07e8d9a4d2c501bbcb56031ccc9
      https://github.com/llvm/llvm-project/commit/56d061ccc5afb07e8d9a4d2c501bbcb56031ccc9
  Author: William Tran-Viet <wtranviet at proton.me>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M libcxx/include/optional

  Log Message:
  -----------
  [libc++][NFC] Add optional<T&> synopsis (#170043)

  Commit: 4a48740831d0f0779780e0bea64ec4a16d9f6d97
      https://github.com/llvm/llvm-project/commit/4a48740831d0f0779780e0bea64ec4a16d9f6d97
  Author: Helena Kotas <hekotas at microsoft.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M clang/lib/CodeGen/CGExpr.cpp
    M clang/test/CodeGenHLSL/BoolVector.hlsl
    A clang/test/CodeGenHLSL/builtins/VectorElementStore.hlsl
    M clang/test/CodeGenHLSL/builtins/lit.hlsl

  Log Message:
  -----------
  [HLSL] Update indexed vector elements individually (#169144)

When an individual element of a vector is updated via indexing into the vector, it needs to be handled as a store operation on that one vector element.

Clang treats vectors as one unit, so a vector element needs to be updated, the whole vector is loaded, the element is modified, and then the whole vector is stored. In HLSL vector elements are handled individually. We need to avoid this load/modify/store sequence to prevent overwriting other vector elements that might be getting updated in parallel.

Fixes #167729

Contributes to #160208.

  Commit: f65c19982d2af7f791115e0b51c095a52ad5da4a
      https://github.com/llvm/llvm-project/commit/f65c19982d2af7f791115e0b51c095a52ad5da4a
  Author: Aiden Grossman <aidengrossman at google.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M clang-tools-extra/clangd/test/CMakeLists.txt
    M clang-tools-extra/clangd/test/include-cleaner-batch-fix.test
    M clang-tools-extra/clangd/test/index-tools.test
    M clang-tools-extra/clangd/test/lit.cfg.py
    M clang-tools-extra/clangd/test/lit.site.cfg.py.in
    M clang-tools-extra/clangd/test/system-include-extractor.test

  Log Message:
  -----------
  Reapply "[clangd] Make lit tests work with the internal shell" (#169972)

This reverts commit bd04ef6df50e8e6e5212762fc798ea9fbdcfc897.

This reapply fixes the broken case where we would fail at CMake
configuration time if LLVM_INCLUDE_BENCHMARKS was explicitly turned off.

  Commit: b73385dda5caa21570ddc6d7277c22aca8f2de1e
      https://github.com/llvm/llvm-project/commit/b73385dda5caa21570ddc6d7277c22aca8f2de1e
  Author: Nico Weber <thakis at chromium.org>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M compiler-rt/cmake/config-ix.cmake

  Log Message:
  -----------
  [TySan] Attempt to unbreak build after #169036

If tysan was not in COMPILER_RT_SANITIZERS_TO_BUILD, we used to
get an error after #169036, see comments there for details.

  Commit: 9edbf83667821e3154446d5e2429e41bf261e26f
      https://github.com/llvm/llvm-project/commit/9edbf83667821e3154446d5e2429e41bf261e26f
  Author: Charles Zablit <c_zablit at apple.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M lldb/source/Host/windows/ProcessLauncherWindows.cpp

  Log Message:
  -----------
  [lldb][windows] fix environment handling in CreateProcessW setup (#168733)

This patch refactors and documents the setup of the `CreateProcessW`
invocation in `ProcessLauncherWindows`. It's a dependency of
https://github.com/llvm/llvm-project/pull/168729.

`CreateEnvironmentBufferW` now sorts the environment variable keys
before concatenating them into a string. From [the `CreateProcess`
documentation](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessw):
> An application must manually pass the current directory information to
the new process. To do so, the application must explicitly create these
environment variable strings, sort them alphabetically (because the
system uses a sorted environment), and put them into the environment
block. Typically, they will go at the front of the environment block,
due to the environment block sort order.

`GetFlattenedWindowsCommandStringW` now returns an error which will be
surfaced, instead of failing silently.

Types were converted to their wide equivalent (i.e appending `W` to
them, see `STARTUPINFOEX`) since we are calling the `W` variant of
`CreateProcess`.

  Commit: 0ff0f52460531c0bfa213d0dcfa0cfb4ba61e934
      https://github.com/llvm/llvm-project/commit/0ff0f52460531c0bfa213d0dcfa0cfb4ba61e934
  Author: Greg Clayton <gclayton at fb.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M llvm/include/llvm/DebugInfo/DWARF/DWARFAcceleratorTable.h
    M llvm/lib/DebugInfo/DWARF/DWARFAcceleratorTable.cpp

  Log Message:
  -----------
  Fix __apple_XXX iterator that iterates over all entries. (#157538)

The previous iterator for __apple_XXX sections was assuming that all
entries in the table would be contiguous and it wasn't using the offsets
table to access each chain of entries for a given name. This patch fixes
it so the iterator does the right thing.

This issue became apparent after a modification to strip template names
from DW_AT_name entries to allow adding both the template class base
name as an entry and also include the name with template names. The
commit hash is 2e7ee4dc21430b0fe4c9ee306dc1d8c7986a6646. The problem is
if the name starts with a "<" it will try and split the name. So if the
name is `"<get-size>"` it will return an empty string as the function
name, and this empty string gets added to the __apple_names table and
causes large delays when using the iterators.

  Commit: e6ae2462bd6dcf583ccd13c6627fe3ffe8a17f2c
      https://github.com/llvm/llvm-project/commit/e6ae2462bd6dcf583ccd13c6627fe3ffe8a17f2c
  Author: Stanislav Mekhanoshin <Stanislav.Mekhanoshin at amd.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M llvm/lib/Target/AMDGPU/GCNHazardRecognizer.cpp
    M llvm/lib/Target/AMDGPU/GCNHazardRecognizer.h

  Log Message:
  -----------
  [AMDGPU] Refactor hazard recognizer for VALU-pipeline hazards. NFCI. (#168801)

This is in preparation of handling these in scheduler. I do not expect
any changes to the produced code here, it is just an infrastructure.
Our current problem with the VALU pipeline hazards is that we only
insert V_NOP instructions in the hazard recognizer mode, but ignore
it during scheduling. This patch is meant to create a mechanism to
actually account for that during scheduling.

  Commit: d200a51ba1d12dc60abaa44095b7242a112eb45e
      https://github.com/llvm/llvm-project/commit/d200a51ba1d12dc60abaa44095b7242a112eb45e
  Author: Stanislav Mekhanoshin <Stanislav.Mekhanoshin at amd.com>
  Date:   2025-12-01 (Mon, 01 Dec 2025)

  Changed paths:
    M clang-tools-extra/clangd/test/CMakeLists.txt
    M clang-tools-extra/clangd/test/include-cleaner-batch-fix.test
    M clang-tools-extra/clangd/test/index-tools.test
    M clang-tools-extra/clangd/test/lit.cfg.py
    M clang-tools-extra/clangd/test/lit.site.cfg.py.in
    M clang-tools-extra/clangd/test/system-include-extractor.test
    M clang/lib/CodeGen/CGExpr.cpp
    M clang/test/CodeGenHLSL/BoolVector.hlsl
    A clang/test/CodeGenHLSL/builtins/VectorElementStore.hlsl
    M clang/test/CodeGenHLSL/builtins/lit.hlsl
    M compiler-rt/cmake/config-ix.cmake
    A flang/include/flang/Optimizer/Transforms/CUDA/CUFAllocationConversion.h
    M flang/include/flang/Optimizer/Transforms/Passes.td
    M flang/lib/Optimizer/Transforms/CMakeLists.txt
    A flang/lib/Optimizer/Transforms/CUDA/CUFAllocationConversion.cpp
    M flang/lib/Optimizer/Transforms/CUFOpConversion.cpp
    M libcxx/include/optional
    M lldb/source/Core/Statusline.cpp
    M lldb/source/Host/windows/ProcessLauncherWindows.cpp
    M lldb/source/Plugins/SymbolFile/NativePDB/SymbolFileNativePDB.cpp
    M lldb/test/API/functionalities/statusline/TestStatusline.py
    A lldb/test/Shell/SymbolFile/NativePDB/find-pdb-next-to-exe.test
    M llvm/include/llvm/DebugInfo/DWARF/DWARFAcceleratorTable.h
    M llvm/lib/DebugInfo/DWARF/DWARFAcceleratorTable.cpp
    M llvm/lib/Target/X86/X86ISelLowering.cpp
    M llvm/test/CodeGen/X86/combine-ffloor.ll
    M llvm/test/CodeGen/X86/combine-fround.ll

  Log Message:
  -----------
  Merge branch 'main' into users/rampitec/11-17-_amdgpu_allow_hazard_checks_for_wmma_co-exec

Compare: https://github.com/llvm/llvm-project/compare/7ab14fcb32d5...d200a51ba1d1

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