Displaying 2 results from an estimated 2 matches for "llvmattributeref".
2012 Oct 18
2
[LLVMdev] [RFC] LLVM C-API Change
...t happens to be the internal bit representation of the Attributes object. This is bad for several reasons, not the least of which is that it's completely inextensible (e.g., we don't have room for LLVMAddressSafety).
I would like to either remove these functions or create a new type called LLVMAttributeRef that references an Attributes object. The controversy is that this breaks the rule that C-APIs cannot change. But I don't really see an alternative, since this representation is going to become invalid with the new changes.
What are people's thoughts on this?
-bw
2012 Oct 18
0
[LLVMdev] [RFC] LLVM C-API Change
...to be the internal bit representation of the Attributes object. This is bad for several reasons, not the least of which is that it's completely inextensible (e.g., we don't have room for LLVMAddressSafety).
>
> I would like to either remove these functions or create a new type called LLVMAttributeRef that references an Attributes object. The controversy is that this breaks the rule that C-APIs cannot change. But I don't really see an alternative, since this representation is going to become invalid with the new changes.
how about having LLVMAttribute be an enum specific to the C-API, and o...