search for: writeroptions

...te subclass of TargetInfo will ultimately hold the flavor specific options. So can DarwinDriver get a copy of the MachOTargetInfo object and set its ivars based on the command line options? Previously, I thought of LinkerOptions as the options needed by the core-linking phase (resolver), and the WriterOptions were flavor specific. Here is how I see it currently works: 1) The flavor determines the driver class instantiated. 2) The driver transforms flavor specific options into a "core" ArgList; 3) LinkerOptions constructor requires a core ArgList and sets ivars base on the ArgList. 4) The...

...te subclass of TargetInfo will ultimately hold the flavor specific options. So can DarwinDriver get a copy of the MachOTargetInfo object and set its ivars based on the command line options? Previously, I thought of LinkerOptions as the options needed by the core-linking phase (resolver), and the WriterOptions were flavor specific. > > Not allowing Drivers to touch anything except for core args has a very > important side effect. We will always be able to test everything > through -core and dump how to run it with -###. LLVM and Clang both > handle options like this, and it seems to scale...

...te subclass of TargetInfo will ultimately hold the flavor specific options. So can DarwinDriver get a copy of the MachOTargetInfo object and set its ivars based on the command line options? Previously, I thought of LinkerOptions as the options needed by the core-linking phase (resolver), and the WriterOptions were flavor specific. Not allowing Drivers to touch anything except for core args has a very important side effect. We will always be able to test everything through -core and dump how to run it with -###. LLVM and Clang both handle options like this, and it seems to scale fine. As an alternative...