search for: attrgroup

.... > > The core of this proposal is the idea of an "attribute group". As the name > implies, it's a group of attributes that are then referenced by objects within > the IR. An attribute group is a module-level object. The BNF of the syntax is: > > attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } > attrgroup_id := #<number> > attribute_list := <attribute> (, <attribute>)* > attribute := <name> (= <value>)? > > To use an attribute group, an object references the attribute group's ID:...

...core of this proposal is the idea of an "attribute group". As the name >> implies, it's a group of attributes that are then referenced by objects within >> the IR. An attribute group is a module-level object. The BNF of the syntax is: >> >> attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } >> attrgroup_id := #<number> >> attribute_list := <attribute> (, <attribute>)* >> attribute := <name> (= <value>)? >> >> To use an attribute group, an object references the attri...

...e core of this proposal is the idea of an "attribute group". As the name >> implies, it's a group of attributes that are then referenced by objects within >> the IR. An attribute group is a module-level object. The BNF of the syntax is: >> >> attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } >> attrgroup_id := #<number> >> attribute_list := <attribute> (, <attribute>)* >> attribute := <name> (= <value>)? >> >> To use an attribute group, an object references the attrib...

...flags specified in the module. The core of this proposal is the idea of an "attribute group". As the name implies, it's a group of attributes that are then referenced by objects within the IR. An attribute group is a module-level object. The BNF of the syntax is: attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } attrgroup_id := #<number> attribute_list := <attribute> (, <attribute>)* attribute := <name> (= <value>)? To use an attribute group, an object references the attribute group's ID: attribute_group_ref...

On Nov 26, 2012, at 3:20 PM, Bill Wendling wrote: >> 4. Do we really want the attribute references limited to a number? Code will be more readable >> if you can use actual names that indicate the intent. For example: >> >> attrgroup #compile_options = { … } >> void @foo attrgroup(#compile_options) >> > The problem with this is it limits the number of attribute groups to a specific set -- compile options, non-compile options, etc.. There could be many different attribute groups involved, especially during...

...l soon have run out of space entirely. Target-Specific Attributes in IR ================================ I propose that the target-specific attributes would be organized into groups. Those groups would then be referenced by the functions directly. Here is an example of what that could look like: attrgroup #1 = { "long-calls", "cpu=cortex-a8", "thumb" } define void @func() noinline ssp attrgroup(#1) { ret void } Each target would know which options it can handle and how to parse them correctly. Code generation would use the attribute group referenced by the function...

> attrgroup #1 = { "long-calls", "cpu=cortex-a8", "thumb" } > > define void @func() noinline ssp attrgroup(#1) { > ret void > } > I like the general idea. Just one clarification: In the above example, are the attributes taken from a list specified in the language...

...t; The core of this proposal is the idea of an "attribute group". As the name > implies, it's a group of attributes that are then referenced by objects > within > the IR. An attribute group is a module-level object. The BNF of the syntax > is: > > attribute_group := attrgroup <attrgroup_id> = { <attribute_list> } > attrgroup_id := #<number> > attribute_list := <attribute> (, <attribute>)* > attribute := <name> (= <value>)? > > To use an attribute group, an object references the attribute group's I...

...fael, Sorry, I forgot to respond to this. They can be arbitrary strings that are known only to the specific back-end. It may be beneficial to define them inside of the LangRef document though. -bw On Oct 4, 2012, at 7:47 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> attrgroup #1 = { "long-calls", "cpu=cortex-a8", "thumb" } >> >> define void @func() noinline ssp attrgroup(#1) { >> ret void >> } >> > > I like the general idea. Just one clarification: In the above example, > are the attributes taken f...

...; > Target-Specific Attributes in IR > ================================ > > I propose that the target-specific attributes would be organized into groups. > Those groups would then be referenced by the functions directly. Here is an > example of what that could look like: > > attrgroup #1 = { "long-calls", "cpu=cortex-a8", "thumb" } > > define void @func() noinline ssp attrgroup(#1) { > ret void > } does this mean you would like attributes to form a tree structure? This sounds a lot like metadata, only metadata that can't be thro...

...specified in the module. The core of this proposal is the idea of an "attribute group". As the name implies, it's a group of attributes that are then referenced by objects within the IR. An attribute group is a module-level object. The BNF of the syntax is: attribute_group := <attrgroup_id> '=' attributes '{' <attribute_list> '}' attrgroup_id := #<id> attribute_list := <attribute> <attribute>* attribute := <name> ('=' <list_of_values>)? list_of_values := <value> | '(' <value&...

> To use an attribute group, an object references the attribute group's ID: > > attribute_group_ref := attrgroup(<attrgroup_id>) Is this unused now? I don't see it anywhere else in the proposal. -- Sean Silva

...ke metadata... What was the reason for not enhancing metadata to cover this use case? I'm sure you explained but I've completely forgotten... Ciao, Duncan. > > -bw > > On Oct 4, 2012, at 7:47 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >>> attrgroup #1 = { "long-calls", "cpu=cortex-a8", "thumb" } >>> >>> define void @func() noinline ssp attrgroup(#1) { >>> ret void >>> } >>> >> >> I like the general idea. Just one clarification: In the above example, >&...

.... > The core of this proposal is the idea of an "attribute group". As the name > implies, it's a group of attributes that are then referenced by objects within > the IR. An attribute group is a module-level object. The BNF of the syntax is: > > attribute_group := <attrgroup_id> '=' attributes '{' <attribute_list> '}' > attrgroup_id := #<id> > attribute_list := <attribute> <attribute>* > attribute := <name> ('=' <list_of_values>)? > list_of_values := <value> | '(...

...aving a #<num> referenced by the object. Kind of like how metadata is referenced. -bw On Feb 3, 2013, at 4:50 PM, Sean Silva <silvas at purdue.edu> wrote: >> To use an attribute group, an object references the attribute group's ID: >> >> attribute_group_ref := attrgroup(<attrgroup_id>) > > Is this unused now? I don't see it anywhere else in the proposal. > > -- Sean Silva

...e of this proposal is the idea of an "attribute group". As the name >> implies, it's a group of attributes that are then referenced by objects within >> the IR. An attribute group is a module-level object. The BNF of the syntax is: >> >> attribute_group := <attrgroup_id> '=' attributes '{' <attribute_list> '}' >> attrgroup_id := #<id> >> attribute_list := <attribute> <attribute>* >> attribute := <name> ('=' <list_of_values>)? >> list_of_values := <value&...