Displaying 3 results from an estimated 3 matches for "valuekind".
Did you mean:
value_kind
2019 Dec 17
2
llvm/docs/AMDGPUUsage.rst ERROR: Malformed table
...string Kernel argument type name.
"Size" integer Required Kernel argument size in bytes.
"Align" integer Required Kernel argument alignment in
bytes. Must be a power of two.
"ValueKind" string Required Kernel argument kind that
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
SW versions:...
2010 Nov 30
0
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
...ase remove this. In its place, we should have a naming rule for public ivars, and for enumerations and enumerators. I'd suggest ivars and enums follow the same rules as types. If there is a doubt, the enum should be a "Kind", e.g. "ValueTy" in llvm/Value.h should be "ValueKind".
Enumerators (unless they are in their own small namespace) should have a prefix. For example, the enumerators in the ValueTy enum should be VK_Argument, VK_BasicBlock, etc. These rules shouldn't apply to enums that are just convenience constants, like:
enum {
MaxSize = 42,
Densit...
2010 Nov 29
3
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
On Sun, Nov 28, 2010 at 11:02 PM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
>> I enjoyed the new coding style in recent patches. Camel case makes it easy
>> to pick a descriptive name. Starting functions and variables with lower
>> cases reduces chances to conflict with a type name.
> Honestly speaking, I don't. Especially in the cases when varname is