for context; https://ghc.haskell.org/trac/ghc/ticket/7602
basically clang built GHC has ~ 15% slowdown vs GCC flavor because of differences in how they do certain details in the RTS on OSX.
i've been doing gcc flavored ghc mac builds for nearly every ghc version to date, and those should be the ones used for ghcup on darwin
What is the proposed course of action? Replace the OSX tarball link with something pointing to the gcc build? Who will maintain it for every GHC release? Does it have better portability?
I’m working with Ben to make sure there’s going to be gcc flavor builds
available for ghc going forward. I’m the main admin on the new OS X ci
hardware for ghc.
There’s no change in portability .. what notion of portability do you have
in mind ?
I’ve spoken with Ben and Hvr about hosting these in the past. Honestly
they should be hosted on haskell dot org infra and I’ve been poking them
about that.
What is the proposed course of action? Replace the OSX tarball link with
something pointing to the gcc build? Who will maintain it for every GHC
release? Does it have better portability?
@cartazio For record, I'm fine with it; it's primarily @bgamari's call as the release-manager what to place into the http://downloads.haskell.org/ghc/ download area