If I understand correctly, the way Hadrian works is that all of the
.conf files, binaries, and so on in _build/stage0 are built with the
bootstrap compiler. I need to write client code that uses the ghc
library built from GHC HEAD (so ghc-9.3), but I'd prefer to use the
bootstrap compiler. (The
On Fri, 11 Feb 2022, ÉRDI Gergő wrote:
Presumably you must also be generating these bindings (in a `ModGuts`
perhaps?) and
generating code for them that will ultimately be linked into the program to
run.
BTW, I thought that linking is done on the object file level, i.e. I
thought it is
On Fri, 11 Feb 2022, Simon Peyton Jones wrote:
A `ModDetails` gives the type signatures for everything, but no actual code.
For
example if you have `f :: Int -> Int` in the `md_types`, the `ModDetails`
doesn't
include the binding `f = rhs` for `f`.
Yes, this on its own makes sense.
A `ModDetails` gives the type signatures for everything, but no actual
code. For example if you have `f :: Int -> Int` in the `md_types`, the
`ModDetails` doesn't include the binding `f = rhs` for `f`.
Presumably you must also be generating these bindings (in a `ModGuts`
perhaps?) and generating
