search for: objectfilewriter

>I like the idea of a generic MachineCodeWriter, although I prefer the >name 'ObjectFileWriter'... Thats much more descriptive of the functionality. >I think we need to take a hard look at which bits of the >Writer/Emitter infrastructure are needed for what tasks (Object File >Emittion, JIT, etc.) and make sure that our abstractions are flexible >enough... I would suggest...

On Sun, Mar 15, 2009 at 10:52 PM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > I like the idea of a generic MachineCodeWriter, although I prefer the >> name 'ObjectFileWriter'... >> > > Thats much more descriptive of the functionality. > 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...

I like the idea of a generic MachineCodeWriter, although I prefer the name 'ObjectFileWriter'... I think we need to take a hard look at which bits of the Writer/Emitter infrastructure are needed for what tasks (Object File Emittion, JIT, etc.) and make sure that our abstractions are flexible enough... As it stands at the moment, the Writer and Emitter classes could definately be merge...

...bject file generation capabilities to include new > object file formats is difficult, and requires modifications to LLVM > code (not just a plugin). > > I suggest transforming the {getMachOWriterInfo, getELFWriterInfo} > functions (on TargetMachine) into a single (templated?) > getObjectFileWriterInfo function. Additionally a addObjectFileWriter > member should be added to TargetMachine, taking the place of the > static {AddMachOWriter, AddELFWriter} functions. > > As I need this functionality (custom object file generation) for my > current target, I'd be happy to make t...

...wants. 2. Extension of the object file generation capabilities to include new object file formats is difficult, and requires modifications to LLVM code (not just a plugin). I suggest transforming the {getMachOWriterInfo, getELFWriterInfo} functions (on TargetMachine) into a single (templated?) getObjectFileWriterInfo function. Additionally a addObjectFileWriter member should be added to TargetMachine, taking the place of the static {AddMachOWriter, AddELFWriter} functions. As I need this functionality (custom object file generation) for my current target, I'd be happy to make the modifications to the...

...16, 2009 at 3:26 AM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Sun, Mar 15, 2009 at 10:52 PM, Aaron Gray < > aaronngray.lists at googlemail.com> wrote: > >> I like the idea of a generic MachineCodeWriter, although I prefer the >>> name 'ObjectFileWriter'... >>> >> >> Thats much more descriptive of the functionality. >> > > 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 wi...