diff options
| author | John Ericson <git@JohnEricson.me> | 2019-03-27 00:27:01 -0400 |
|---|---|---|
| committer | Ben Gamari <ben@smart-cactus.org> | 2019-05-14 16:41:19 -0400 |
| commit | e529c65eacf595006dd5358491d28c202d673732 (patch) | |
| tree | 0498cb0a7023c491c240d64069e2442073e83d77 /compiler/main/GhcMake.hs | |
| parent | f9e4ea401121572d799b9db56f24aa1abdf5edf8 (diff) | |
| download | haskell-e529c65eacf595006dd5358491d28c202d673732.tar.gz | |
Remove all target-specific portions of Config.hs
1. If GHC is to be multi-target, these cannot be baked in at compile
time.
2. Compile-time flags have a higher maintenance than run-time flags.
3. The old way makes build system implementation (various bootstrapping
details) with the thing being built. E.g. GHC doesn't need to care
about which integer library *will* be used---this is purely a crutch
so the build system doesn't need to pass flags later when using that
library.
4. Experience with cross compilation in Nixpkgs has shown things work
nicer when compiler's can *optionally* delegate the bootstrapping the
package manager. The package manager knows the entire end-goal build
plan, and thus can make top-down decisions on bootstrapping. GHC can
just worry about GHC, not even core library like base and ghc-prim!
Diffstat (limited to 'compiler/main/GhcMake.hs')
| -rw-r--r-- | compiler/main/GhcMake.hs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler/main/GhcMake.hs b/compiler/main/GhcMake.hs index d730fe70f1..fe4c9781e2 100644 --- a/compiler/main/GhcMake.hs +++ b/compiler/main/GhcMake.hs @@ -1953,7 +1953,7 @@ downsweep hsc_env old_summaries excl_mods allow_dup_roots -- See Note [-fno-code mode] #8025 map1 <- if hscTarget dflags == HscNothing then enableCodeGenForTH - (defaultObjectTarget (targetPlatform dflags)) + (defaultObjectTarget (settings dflags)) map0 else return map0 return $ concat $ nodeMapElts map1 |