Skip to content

[pull] main from llvm:main#1918

Merged
pull[bot] merged 9 commits into
realqhc:mainfrom
llvm:main
Jun 8, 2026
Merged

[pull] main from llvm:main#1918
pull[bot] merged 9 commits into
realqhc:mainfrom
llvm:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Jun 8, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

dzbarsky and others added 9 commits June 8, 2026 00:39
The use-def list is circular in the Prev direction (Head->Prev == Tail)
and defs always precede uses, see
MachineRegisterInfo::addRegOperandToUseList().

We can implement hasOneUse() by checking only the Tail and its Prev,
instead of
walking past all defs from the head via use_iterator.
…age changes (#202244)

Fix tests after #195308 ([AtomicExpand] Preserve flags expanding
loads/stores to cmpxchg/atomicrmw) and ([CodeGen][NFC] Remove
contractions in error messages).
…201755)

DenseMap no longer use in-band sentinel keys. (#200595 and #201281).
Update the GDB pretty printer and LLDB data formatters to test the used
bit rather than comparing keys.

GDB: advancePastEmptyBuckets relied on DenseMapInfo::getEmptyKey(),
which could not be evaluated in GDB and so was disabled, leaving the printer
to emit empty and erased buckets. It now walks bucket indices and skips any
whose used bit is clear.

LLDB: DenseMapSynthetic used a key-uniqueness heuristic to guess which
buckets were live, which mishandled a lone erased bucket (hence the
former tombstones=1 summary note). It now reads the used array directly,
so erased entries are skipped exactly. NumTombstones no longer exists,
so drop it from the summary.

Written by Claude Opus 4.8

---------

Co-authored-by: Dave Lee <davelee.com@gmail.com>
Fixed the misleading note location for inferred ID-dependent fields.
Now the note points to the assignment that introduces the dependency,
not the field declaration.

Fixes #202077
…202247)

This commit encountered PCH related errors on buildbot, so revert it for
now.
…X=64 is specified (#201822)

The issue is exposed in #201773, where LLVM_FOUND is 0 in libclc in
in-tree build.
As pointed out in
https://discourse.llvm.org/t/libclang-python-binding-tests-seem-inefficient/90984/3,
the latest Python version currently used in the bindings tests is not
the latest stable version.
Upgrade to the latest stable Python version (3.14), see here:
https://devguide.python.org/versions/
@pull pull Bot locked and limited conversation to collaborators Jun 8, 2026
@pull pull Bot added the ⤵️ pull label Jun 8, 2026
@pull pull Bot merged commit 4e3a209 into realqhc:main Jun 8, 2026
17 of 18 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants