If you're working on e.g. ARM, you may not have a lot of say in how much
RAM you can put into it.
On Wed, Aug 8, 2018 at 6:54 PM Michael Sloan wrote:
> Good point, I have added a note about it to the wiki page. Surprising
> that it would be hard to kill. Do you have swap setup?
>
> For me it
Good point, I have added a note about it to the wiki page. Surprising
that it would be hard to kill. Do you have swap setup?
For me it takes ~2.7GB initially and 3.5GB after the first reload. In
the past I've seen it get all the way up to 9GB so there may be some
memory leakage.
I have 40GB
In practice, how much memory does this use?
I find that with 4gb of memory that it is unusable and hard to kill.
Perhaps we should add some sort of warning to the page about this.
Cheers
Matt
On Wed, Aug 8, 2018 at 11:12 PM, Michael Sloan wrote:
> Now that [D5015] is merged (thanks,
Now that [D5015] is merged (thanks, monoidal!), -fobject-code no
longer needs to be provided manually. This also means that you can
run [ghcid] directly in the root of the repo without any arguments. I
have updated https://ghc.haskell.org/trac/ghc/wiki/Building/InGhci to
use the simpler
Thanks a bunch for updating the wiki page, Artem! It was on my todo
list, but it's been a rather busy week. I've added an update
mentioning that it will be possible to run "ghcid" directly without
args once D5105 is merged.
On Mon, Aug 6, 2018 at 12:55 AM, Artem Pelenitsyn
wrote:
> I added
I added this to the wiki. It would be nice to have a wrapper similar to
`run.sh` but for starting ghcid, I believe.
--
Best wishes,
Artem
On Sun, 29 Jul 2018 at 10:41 Matthew Pickering
wrote:
> Can you please update the wiki page?
>
> https://ghc.haskell.org/trac/ghc/wiki/Building/InGhci
>
>
Can you please update the wiki page?
https://ghc.haskell.org/trac/ghc/wiki/Building/InGhci
Matt
On Sun, Jul 29, 2018 at 6:18 AM, Michael Sloan wrote:
> Hello GHC developers!
>
> Now that D4904 and D4986 are merged, if you have recently built GHC
> then you can use "./utils/ghc-in-ghci/run.sh
Hello GHC developers!
Now that D4904 and D4986 are merged, if you have recently built GHC
then you can use "./utils/ghc-in-ghci/run.sh -fobject-code" to load
GHC into GHCi (throwing on a "-j8" helps too). For me, this makes
development far more pleasant, as often I can make a change and try it
