search for: emitoperand

...ction, using MachineCodeEmitter::emit* functions - call MachOCodeEmitter::finishFunction [This runOnMachineFunction could definitely be generalized, i.e. implemented in a base class ('EmitterMachineFunctionPass' or a better name). This base class would then have (abstract) emitInstruction, emitOperand, etc... methods. It should also integrate with the *GenCodeEmitter emitted by tblgen so that you get automatic code emission. When implementing a new target, one would simply need to inherit the baseclass, and override the functions necessary to tweak output.]

>> 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.

...er::emit* functions > - call MachOCodeEmitter::finishFunction > > [This runOnMachineFunction could definitely be generalized, i.e. > implemented in a base class ('EmitterMachineFunctionPass' or a better > name). This base class would then have (abstract) emitInstruction, > emitOperand, etc... methods. It should also integrate with the > *GenCodeEmitter emitted by tblgen so that you get automatic code > emission. When implementing a new target, one would simply need to > inherit the baseclass, and override the functions necessary to tweak > output.] runOnMachineFunct...