search for: addpassestoemitobject

...e something along the lines of "add function" or "add global var"? * Alexander: yes * Chris: no, make it more abstract. create a template class whose parameter is an object file writer that the various targets can use to implement a new TargetMachine::addPassesToEmitObject 4. Do we want to expose arbitrary construction of ELF/COFF? * Reid: no * Alexander: no * Chris: no, keep ELF/COFF implementations separate So, here's the plan: 1. No reading interface. To have a system agnostic interface for reading a dynamic library, use System/DynamicLibr...

...o/.obj file output. There will be no > support for .exe or .a output. Sounds good. > 3. The interface will deal with ELF and COFF output separately with > separate interfaces for them. Sounds good. > 4. If Chris will expound on his design for the way to implement > TargetMachine::addPassesToEmitObject, that sounds like a good way to go. > However, doesn't this mean the ELF/COFF interfaces should be at the same > level? I'm looking at the X86/X86CodeEmitter.cpp file and the various > methods for emitting instructions/blocks/addresses/etc. Shouldn't the > ELF/COFF interface...