Displaying 3 results from an estimated 3 matches for "finalsize".
Did you mean:
finalize
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
2008 Apr 16
0
[LLVMdev] Being able to know the jitted code-size before emitting
...}
> +
> +static unsigned sizeRegModRMByte(){
> + return 1;
> +}
> +
> +static unsigned sizeSIBByte(){
> + return 1;
> +}
> +
> +static unsigned sizeDisplacementField(const MachineOperand
> *RelocOp) {
How about getDisplacementFieldSize()?
>
> + unsigned FinalSize = 0;
> + // If this is a simple integer displacement that doesn't require
> a relocation,
> + // emit it now.
> + if (!RelocOp) {
> + FinalSize += sizeConstant(4);
> + return FinalSize;
> + }
> +
> + // Otherwise, this is something that requires a relocat...
2008 Apr 15
4
[LLVMdev] Being able to know the jitted code-size before emitting
OK, here's a new patch that adds the infrastructure and the
implementation for X86, ARM and PPC of GetInstSize and GetFunctionSize.
Both functions are virtual functions defined in TargetInstrInfo.h.
For X86, I moved some commodity functions from X86CodeEmitter to
X86InstrInfo.
What do you think?
Nicolas
Evan Cheng wrote:
>
> I think both of these belong to TargetInstrInfo. And