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 /includes | |
| 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 'includes')
| -rw-r--r-- | includes/ghc.mk | 17 |
1 files changed, 16 insertions, 1 deletions
diff --git a/includes/ghc.mk b/includes/ghc.mk index 71941c9d50..2421d9ca96 100644 --- a/includes/ghc.mk +++ b/includes/ghc.mk @@ -211,8 +211,23 @@ $(includes_SETTINGS) : includes/Makefile | $$(dir $$@)/. @echo ',("LLVM llc command", "$(SettingsLlcCommand)")' >> $@ @echo ',("LLVM opt command", "$(SettingsOptCommand)")' >> $@ @echo ',("LLVM clang command", "$(SettingsClangCommand)")' >> $@ + @echo + @echo ',("integer library", "$(INTEGER_LIBRARY)")' >> $@ + @echo ',("Use interpreter", "$(GhcWithInterpreter)")' >> $@ + @echo ',("Use native code generator", "$(GhcWithNativeCodeGen)")' >> $@ + @echo ',("Support SMP", "$(GhcWithSMP)")' >> $@ + @echo ',("RTS ways", "$(GhcRTSWays)")' >> $@ @echo ',("Tables next to code", "$(GhcEnableTablesNextToCode)")' >> $@ - @echo ']' >> $@ + @echo ',("Leading underscore", "$(LeadingUnderscore)")' >> $@ + @echo ',("Use LibFFI", "$(UseLibFFIForAdjustors)")' >> $@ +# Note that GhcThreaded just reflects the Makefile variable setting. In +# particular, the stage1 compiler is never actually compiled with -threaded, but +# it will nevertheless have cGhcThreaded = True. The "+RTS --info" output will +# show what RTS GHC is really using. + @echo ",(\"Use Threads\", \"$(GhcThreaded)\")" >> $@ + @echo ",(\"Use Debugging\", \"$(GhcDebugged)\")" >> $@ + @echo ",(\"RTS expects libdw\", \"$(GhcRtsWithLibdw)\")" >> $@ + @echo "]" >> $@ # --------------------------------------------------------------------------- |