[all-commits] [llvm/llvm-project] edb80a: [lldb][test] Fix bf16 test cases on Arm 32-bit (#1...

[David Spickett via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: edb80a8d7fb2e1e29a4cb792148b4ffd441eb114
      https://github.com/llvm/llvm-project/commit/edb80a8d7fb2e1e29a4cb792148b4ffd441eb114
  Author: David Spickett <david.spickett at linaro.org>
  Date:   2025-10-01 (Wed, 01 Oct 2025)

  Changed paths:
    M lldb/test/API/lang/cpp/floating-types-specialization/TestCppFloatingTypesSpecialization.py
    M lldb/test/API/lang/cpp/template-arguments/TestCppTemplateArguments.py

  Log Message:
  -----------
  [lldb][test] Fix bf16 test cases on Arm 32-bit (#161528)

Fixes #157674

On ARM, the presence of a specific bf16 type in the AST is gated by: 
```
bool ARMTargetInfo::hasBFloat16Type() const {
  // The __bf16 type is generally available so long as we have any fp registers.
  return HasBFloat16 || (FPU && !SoftFloat);
}
```

And the target we use when evaluating symbols (derived from the program
file, I think, haven't found it yet) does not enable any of this.

This means that we fall back to __fp16.

So for parts of the testing we just need to expect __fp16 instead, and
others we need to skip because now a class looks like it inherits from
itself.

There's a proper fix here somewhere but I don't know what it is yet.



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