Displaying 3 results from an estimated 3 matches for "machowritt".
Did you mean:
machowriter
2009 Mar 16
0
[LLVMdev] MachO and ELF Writers/MachineCodeEmittersarehard-codedinto LLVMTargetMachine
...uldn't these be pushed into the
MachOWriter? ]
3. X86CodeEmitter
- a MachineFunctionPass, NOT a MachineCodeEmitter (Could the naming
change perhaps?)
This class receives (during construction) a reference to a
MachineCodeEmitter (e.g. MachOCodeEmitter, which in turn stores a
reference to a MachOWritter).
The runOnMachineFunction for the X86CodeEmitter does:
- call MachOCodeEmitter::startFunction
- for each basicblock in function:
- call MachOCodeEmitter::StartMachineBasicBlock
- for each instruction in basicblock:
- emit instruction, using MachineCodeEmitter::emit* functions
- cal...
2009 Mar 16
2
[LLVMdev] MachO and ELF Writers/MachineCodeEmittersarehard-codedinto LLVMTargetMachine
>> Sorry, I disagree actually the MachineCodeEmitter or the
>> 'MachineCodeWritter' does not do any file handling at all. Do look at the
>> code for the MachineCodeWritter and you will see it only writes to memory
>> and if it reaches the end of the allotted memory I believe higher ordered
>> logic reallocates a larget buffer and starts again from scratch.
2009 Mar 16
2
[LLVMdev] MachO and ELFWriters/MachineCodeEmittersarehard-codedinto LLVMTargetMachine
...neCodeEmitter (Could the naming
> change perhaps?)
Yes, it uses a MachineCodeEmitter in its internals (MCE) and as a
constructor argument.
> This class receives (during construction) a reference to a
> MachineCodeEmitter (e.g. MachOCodeEmitter, which in turn stores a
> reference to a MachOWritter).
>
> The runOnMachineFunction for the X86CodeEmitter does:
> - call MachOCodeEmitter::startFunction
> - for each basicblock in function:
> - call MachOCodeEmitter::StartMachineBasicBlock
> - for each instruction in basicblock:
> - emit instruction, using MachineCod...