Displaying 6 results from an estimated 6 matches for "machinecodewriter".
Did you mean:
machinecodewritter
2009 Mar 15
3
[LLVMdev] MachO and ELF Writers/MachineCodeEmitters arehard-codedinto LLVMTargetMachine
>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 abs...
2009 Mar 16
0
[LLVMdev] MachO and ELF Writers/MachineCodeEmitters arehard-codedinto LLVMTargetMachine
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 Machi...
2009 Mar 15
1
[LLVMdev] MachO and ELF Writers/MachineCodeEmitters are hard-codedinto LLVMTargetMachine
...e and llc.
I am also interested in working on this area and interested in writting a
COFF file backend.
> In other words, the 'object file generation' capabilities of the
> Common Code Generator are not generic.
I was looking at making a parallel class to MachineCodeEmitter,
'MachineCodeWriter' that can be used generically instead of
MachineCodeEmitter to write to a supplied 'vector<byte>'. This would not
introduce any overhead to the existing runtime code and would allow inlining
of writting functions in X86CodeEmitter and other emitters. They would have
to be temp...
2009 Mar 15
0
[LLVMdev] MachO and ELF Writers/MachineCodeEmitters are hard-codedinto LLVMTargetMachine
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 Wr...
2009 Mar 15
2
[LLVMdev] MachO and ELF Writers/MachineCodeEmitters are hard-coded into LLVMTargetMachine
Currently, the MachO and ELF Writers and MachineCodeEmitters are
hard-coded into LLVMTargetMachine and llc.
In other words, the 'object file generation' capabilities of the
Common Code Generator are not generic.
LLVMTargetMachine::addPassesToEmitFile explicitly checks whether the
derived backend TargetMachine implements one of getMachOWriterInfo or
getELFWriterInfo, and returns a
2009 Mar 16
2
[LLVMdev] MachO and ELF Writers/MachineCodeEmitters arehard-codedinto LLVMTargetMachine
On Mon, Mar 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....