================
@@ -624,29 +624,42 @@ def CIR_VoidType : CIR_Type<"Void", "void"> {
//===----------------------------------------------------------------------===//
// RecordMemberKind
//
-// What a record member holds, for members that do not hold source data.
+// What a record member holds, and whether its extent is a declared one.
//===----------------------------------------------------------------------===//
def CIR_RecordMemberKind : CIR_I32EnumAttr<
"RecordMemberKind", "what a record member holds", [
I32EnumAttrCase<"Data", 0, "data">,
I32EnumAttrCase<"Pad", 1, "pad">,
- I32EnumAttrCase<"Empty", 2, "empty">
+ I32EnumAttrCase<"Empty", 2, "empty">,
----------------
erichkeane wrote:
I see the justification for `bitfield` now I think. I think emitting the
`empty` array is useful, and I think I see that will be long-term necessary.
Re the zero-width-bitfield: DO we have to represent it in the type at all?
What happens if we remove it and leave `ZB` to be just data + pad?
https://github.com/llvm/llvm-project/pull/216864
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
