I'm currently working on a bug and one of the things I often want to know is
what's on the stack. The problem is I can't see labels of continuations so the
information is really useless. Example:
>>> call printStack(((StgTSO*)0x42000e0198)->stackobj)
0x42000c8788: RET_SMALL (0x512d70)
Hi Simon and Peter,
I just wanted to draw your attention to !337 [1], where I try to fix
#15994. While it's possible I have missed something, it looks to me like
there has been a bug lurking here for quite some time. In particular on
a weak memory model machine we do not place a write barrier
Hi Eric,
Good to hear you managed to build GHC both with Make and Hadrian.
Best wishes with your first GHC patch!
Cheers,
Andrey
From: Eric Crockett [mailto:ecrocke...@gmail.com]
Sent: 09 February 2019 18:21
To: Andrey Mokhov
Subject: Re: Cannot build with Hadrian
Andrey,
I had already
I wholly share this concern, which is why I commented on the Phab diff:
> Does this rely on the caller to call dL on the pattern? Very fragile, let's
> not do that.
In addition, I'm worried about illegal states where we end up with
multiple nested levels of `NewPat`, and calling `dL` once is
