search for: returnindex

...ngs about them (like noalias, nonnull, etc.). How this might work: 1. Instead of only CallInst/InvokeInst having an AttributeSet member variable, all instructions would have one. Accessor functions like getAttributes would be moved from CallInst/InvokeInst to Instruction. Only 'AttributeSet::ReturnIndex' would be meaningful on most instructions. 2. For the text IR format: Like with call/invoke currently, we'd optionally parse attributes in between the instruction name ('load', etc.) and the first type parameter. So load would become: <result> = load [ret attrs] [volatile]...

...ects for each kind of object that may have an attribute associated with it: the function as a whole, the return type, or the function's parameters. A function's attributes are at index "AttributeSet::FunctionIndex"; the return type's attributes are at index "AttributeSet::ReturnIndex"; and the function's parameters' attributes are at indices 1, ..., n (where 'n' is the number of parameters). Most methods on the AttributeSet class take an index parameter. An AttributeSet is also a uniqued and immutable object. You create an AttributeSet through the "At...

...ect that may have an attribute associated with it: the function as a > whole, the return type, or the function's parameters. A function's > attributes > are at index "AttributeSet::FunctionIndex"; the return type's attributes > are at > index "AttributeSet::ReturnIndex"; and the function's parameters' > attributes are > at indices 1, ..., n (where 'n' is the number of parameters). Most methods > on > the AttributeSet class take an index parameter. > > An AttributeSet is also a uniqued and immutable object. You create an >...