BSD Commit Log Search

add source type pre-condition

[AMDGPU] Generate checks for many MC tests (#175174)

Generate checks for all tests where that did not change the number of
checks with each prefix, and where the resulting test still passed.

gtk2: Fix gcc 14 build.

Revert "[ORC] Add utilities for limited symbolication of JIT backtraces (#175099)"

This reverts commit 906b48616c03948a4df62a5a144f7108f3c455e8.

The forward fix for this got reverted in
25976e83606f1a7615e3725e6038bb53ee96c3d5, so reverting the original
commit given it is still broken and the forward fix that mitigated most
of the issues is no longer in tree.

[libc][wctype] Upstream StdRng from PtrHash-cc prototype to LLVM libc

[libc][wctype] Upstream immintrin storage from PtrHash-cc prototype to LLVM libc

fix extension

[libc][wctype] Upstream fastrand from PtrHash-cc prototype to LLVM libc

add tests

fix nesting

[libc][wctype] Upstream enumerate header from PtrHash-cc prototype to LLVM libc

Revert "[LLDB] Swig python extensions tests for SBTargetExtention" (#175251)

Reverts llvm/llvm-project#173473

fix nesting

include range and chunk utils

add tests

Add bounds checking asserts

fix nesting

[libc][wctype] Upstream common utils header file from PtrHash-cc prototype to LLVM libc

rename method to `slice_form_range`

add docs comment

fix some warnings and errors

call explicit operator

[libc][wctype] Upstream custom slice implementation from PtrHash-cc prototype to LLVM libc

remove explicit U

make type size_t

format

Add a flag to preserve the old macro behaviour. (#174895)

[Clang][DebugInfo] Add a flag to use expansion loc for macro params.

This patch adds a flag to allow users to preserve the old behaviour -
use the macro expansion location for parameters. This is useful for
wider testing of sample profile driven PGO which relies on debug
information based mapping. This flag is intended to be temporary
and should be safe to remove by EOY 2026. Filed #175249 to
track the cleanup.

---------

Assisted-by: Gemini

[lldb] Fix TestMultithreaded.py when libc++ symbols are present (#174664)

There are a few test cases in TestMultithreaded.py. Most of them set a
breakpoint by name on "next". There's no problem with doing that, but
one of the tests cases in particular relies on being able to grab a
specific breakpoint location corresponding to the test inferior.

If you have libc++ symbols, this test will also have breakpoint
locations for symbols named `next` in libc++. I could have changed the
test to find the correct `next` breakpoint location, but it seems easier
to give it a more uncommon name instead.

   net/curl: update to 8.18.0

   Includes fixes for
   CVE-2025-14524: bearer token leak on cross-protocol redirect
   CVE-2025-14819: OpenSSL partial chain store policy bypass

Fix