[all-commits] [llvm/llvm-project] cc5111: [LLVMABI] Handle Atomic types in the LLVM ABI libr...

Andy Kaylor via All-commits all-commits at lists.llvm.org
Fri Sep 11 09:19:43 PDT 2026


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: cc511140cf7437110de89e779e8328ad565aa2f1
      https://github.com/llvm/llvm-project/commit/cc511140cf7437110de89e779e8328ad565aa2f1
  Author: Andy Kaylor <akaylor at nvidia.com>
  Date:   2026-09-11 (Fri, 11 Sep 2026)

  Changed paths:
    M clang/lib/CodeGen/QualTypeMapper.cpp
    A clang/test/CIR/CodeGen/call-conv-lowering-x86_64-atomic.c
    A clang/test/CodeGen/X86/x86_64-atomic-abi.c
    M llvm/include/llvm/ABI/IRTypeMapper.h
    M llvm/include/llvm/ABI/Types.h
    M llvm/lib/ABI/IRTypeMapper.cpp
    M llvm/lib/ABI/TargetInfo.cpp
    M llvm/unittests/ABI/IRTypeMapperTest.cpp
    M llvm/unittests/ABI/TypesTest.cpp
    M llvm/unittests/ABI/X86TargetInfoTest.cpp

  Log Message:
  -----------
  [LLVMABI] Handle Atomic types in the LLVM ABI library (#221367)

The LLVM ABI library's type system had no way to represent atomic types,
so Clang's QualTypeMapper was just mapping them directly to the
underlying value type. This resulted in mis-classification of some
function signatures involving atomic types.

This change adds AtomicType to the ABI type system and QualTypeMapper.
The actual classification didn't require any updates. Simply having the
atomic type as a distinct type was sufficient for it to produce the
expected results.

Assisted-by: Cursor / various models



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