[all-commits] [llvm/llvm-project] 50faea: [llvm] Use conventional enum declarations (NFC) (#...
Kazu Hirata via All-commits
all-commits at lists.llvm.org
Tue Nov 4 07:13:16 PST 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 50faea28fb93c5938391fdc0a2cfd70b28280537
https://github.com/llvm/llvm-project/commit/50faea28fb93c5938391fdc0a2cfd70b28280537
Author: Kazu Hirata <kazu at google.com>
Date: 2025-11-04 (Tue, 04 Nov 2025)
Changed paths:
M llvm/lib/Target/AArch64/AArch64FastISel.cpp
M llvm/lib/Target/AMDGPU/GCNHazardRecognizer.cpp
M llvm/lib/Target/AMDGPU/GCNNSAReassign.cpp
M llvm/lib/Target/ARM/ARMFastISel.cpp
M llvm/lib/Target/Mips/MipsFastISel.cpp
M llvm/lib/Target/WebAssembly/WebAssemblyFastISel.cpp
M llvm/lib/Target/X86/X86VZeroUpper.cpp
M llvm/unittests/ADT/FallibleIteratorTest.cpp
Log Message:
-----------
[llvm] Use conventional enum declarations (NFC) (#166318)
This patch replaces:
using Foo = enum { A, B, C };
with the more conventional:
enum Foo { A, B, C };
These two enum declaration styles are not identical, but their
difference does not matter in these .cpp files. With the "using Foo"
style, the enum is unnamed and cannot be forward-declared, whereas the
conventional style creates a named enum that can be. Since these
changes are confined to .cpp files, this distinction has no practical
impact here.
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