Displaying 3 results from an estimated 3 matches for "hasalign".
Did you mean:
disalign
2012 Sep 19
8
[LLVMdev] [RFC] Overhauling Attributes
...LLVM objects will be done with simple 'add*' methods:
An example syntax could be:
// Building an Attribute
Attributes A;
A.addAlignAttr(4)
.addNoUnwindAttr()
.addStackProtectorAttr()
.addUnwindTableAttr()
.addReadNoneAttr();
// Querying an Attribute
if (!A.hasStackProtector() || A.hasAlign(4))
...
The Attributes class will be expanded in the future to support code generation
and target-specific options. But it won't require a massive rewrite of the
compiler to do so.
The bit-wise operations on the Attributes class will need to be removed. This is
because the internals of the...
2012 Sep 19
0
[LLVMdev] [RFC] Overhauling Attributes
...uld end up
looking like:
Attributes Base = ...;
Attributes A = Attributes::Builder(Base).addNoUnwind()
.addStackProtector()
.addAlign(4);
>
> // Querying an Attribute
>
> if (!A.hasStackProtector() || A.hasAlign(4))
> ...
>
> The Attributes class will be expanded in the future to support code
> generation
> and target-specific options. But it won't require a massive rewrite of the
> compiler to do so.
>
> The bit-wise operations on the Attributes class will need to be removed...
2012 Sep 20
0
[LLVMdev] [RFC] Overhauling Attributes
...n example syntax could be:
>
> // Building an Attribute
>
> Attributes A;
> A.addAlignAttr(4)
> .addNoUnwindAttr()
> .addStackProtectorAttr()
> .addUnwindTableAttr()
> .addReadNoneAttr();
>
> // Querying an Attribute
>
> if (!A.hasStackProtector() || A.hasAlign(4))
> ...
>
> The Attributes class will be expanded in the future to support code generation
> and target-specific options. But it won't require a massive rewrite of the
> compiler to do so.
>
> The bit-wise operations on the Attributes class will need to be removed. Th...