Displaying 3 results from an estimated 3 matches for "addalign".
Did you mean:
add_align
2008 Apr 17
1
[LLVMdev] Being able to know the jitted code-size before emitting
Thx again Evan for the review. Here's a new patch for the JIT in itself.
The major changes are:
1) A JITMemoryManager now has a flag saying "I require to know the size
of what you want to emit"
2) DwarfJITEmitter is augmented with GetSize* functions
3) JITEmitter::startFunction checks if the JITMemoryManager requires to
know the size. If so, it computes it and gives it through the
2012 Sep 19
0
[LLVMdev] [RFC] Overhauling Attributes
...have some more detailed comments, but nothing really substantive.
Minor API comment as that seems more immediate:
On Wed, Sep 19, 2012 at 3:25 PM, Bill Wendling <wendling at apple.com> wrote:
> An example syntax could be:
>
> // Building an Attribute
>
> Attributes A;
> A.addAlignAttr(4)
> .addNoUnwindAttr()
> .addStackProtectorAttr()
> .addUnwindTableAttr()
> .addReadNoneAttr();
>
Personally, I would prefer to make the Attributes class be immutable, and
the building happen in a helper. One possible interface would end up
looking like:
Attributes Base =...
2012 Sep 19
8
[LLVMdev] [RFC] Overhauling Attributes
...allow the implementation to be swapped out independently of all the clients
changing. It would then expose a very simple predicate interface. Building
attributes for 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'...