GHC.Driver.Pipeline.Execute

The default mechanism to run a pipeline, see Note [The Pipeline Monad]

Default interpretation of each phase, in terms of IO.

Run the JS Backend postHsc phase.

Deal with foreign JS files (embed them into .o files)

Calculate the ModLocation from the provided DynFlags. This function is only used in one-shot mode and therefore takes into account the effect of -o/-ohi flags (which do nothing in --make mode)

Computes the next output filename for something in the compilation pipeline. This is controlled by several variables:

1. Phase: the last phase to be run (e.g. stopPhase). This is used to tell if we're in the last phase or not, because in that case flags like -o may be important.

2. PipelineOutput: is this intended to be a Temporary or Persistent build output? Temporary files just go in a fresh temporary name.

3. String: what was the basename of the original input file?

4. DynFlags: the obvious thing

5. Phase: the phase we want to determine the output filename of.

6. Maybe ModLocation: the ModLocation of the module we're compiling; this can be used to override the default output of an object file. (TODO: do we actually need this?)

LLVM Options. These are flags to be passed to opt and llc, to ensure consistency we list them in pairs, so that they form groups.

What phase to run after one of the backend code generators has run

See Note [Object merging].