-
Notifications
You must be signed in to change notification settings - Fork 697
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Always pass `ghc-options` The [documentation for `ghc-shared-options`][1] states that they are combined with `ghc-options`: > Additional options for GHC when the package is built as shared > library. The options specified via this field are combined with the > ones specified via `ghc-options`, and are passed to GHC during both > the compile and link phases. However, _only_ `ghc-shared-options` and not `ghc-options` are passed in many cases. This is an issue because it requires setting `ghc-shared-options` even if the shared (dynamic) parts of the build don't actually need different options; this has the unpleasant side-effect of causing modules to be compiled twice, effectively doubling compile time! See here, where any non-empty `ghc-shared-options` causes Cabal to not set `-dynamic-too`: https://github.com/haskell/cabal/blob/acbc0f3a5cc9faf0913ff3e270196693816cec41/Cabal/src/Distribution/Simple/GHC.hs#L1466-L1469 This issue was discovered while integrating the `mold` linker with a Haskell project. [1]: https://cabal.readthedocs.io/en/latest/cabal-package.html#pkg-field-ghc-shared-options * Add documentation * Also enhance profArgs and profDynArgs --------- Co-authored-by: Hécate Moonlight <[email protected]> Co-authored-by: Hécate <[email protected]> (cherry picked from commit 9c775f2)
- Loading branch information
Showing
3 changed files
with
38 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
synopsis: Always pass `ghc-options` to GHC | ||
packages: Cabal | ||
prs: #8717 | ||
issues: | ||
|
||
description: { | ||
|
||
Previously, options set in the package field `ghc-options` would not be passed | ||
to GHC during the link phase for shared objects (where multiple `.o` or | ||
`.dyn_o` files are merged into a single object file). This made it impossible | ||
to use `ghc-options` to use a different linker by setting (for example) | ||
`ghc-options: -optl-fuse-ld=mold -optlm-fuse-ld=mold`; the options would be | ||
dropped in the link phase, falling back to the default linker. | ||
|
||
It was possible to work around this by duplicating the `ghc-options` to | ||
`ghc-shared-options`, which _are_ passed in the shared link phase, but that had | ||
the (undocumented and unfortunate) side-effect of disabling the GHC | ||
`-dynamic-too` flag, effectively doubling compilation times when | ||
`ghc-shared-options` are set. | ||
|
||
Now, `ghc-options` are combined with `ghc-shared-options` (to accurately | ||
reflect the documentation on this feature) and the fact that | ||
`ghc-shared-options` disables `-dynamic-too` is documented. | ||
|
||
} |