Re: Linking problem

2019-10-30 Thread Ben Gamari
Ben Gamari writes: > Simon Peyton Jones via ghc-devs writes: > >> Devs >> On the branch wip/inline-compulsory, I'm getting a strange link error: >> > I have a build running now to try to reproduce the issue. > > The fact that stg_marked_upt_frame_ret isn't defined in Updates.o is > bizarre as th

Re: Handling source locations in HsSyn via TTG

2019-10-30 Thread Spiwack, Arnaud
Agreed: it doesn't affect the heap layout, just the types. My reading of the wiki page was not that the heap indirection was the main motivation for this little enquiry, though. Rather some type annoyance things. I don't know that E is the best solution, or even a good solution: I just think it des

Re: users-guide page for master branch

2019-10-30 Thread Takenobu Tani
Thanks for your explanation. I'll check again after the Windows issue is fixed. Thanks, Takenobu On Wed, Oct 30, 2019 at 10:27 PM Ben Gamari wrote: > > Indeed, this is because of the fact that the Windows build is currently > failing due to hsc2hs issues. I have been ignoring the documentation

Re: Linking problem

2019-10-30 Thread Ben Gamari
Simon Peyton Jones via ghc-devs writes: > Devs > On the branch wip/inline-compulsory, I'm getting a strange link error: > I have a build running now to try to reproduce the issue. The fact that stg_marked_upt_frame_ret isn't defined in Updates.o is bizarre as the definition site of that symbol l

Re: users-guide page for master branch

2019-10-30 Thread Ben Gamari
Indeed, this is because of the fact that the Windows build is currently failing due to hsc2hs issues. I have been ignoring the documentation build until the Windows issue has been resolved. Thanks for checking though. Don't hesitate to mention this again if you notice the build is still failing

Re: Handling source locations in HsSyn via TTG

2019-10-30 Thread Sebastian Graf
> I would like to submit a solution E, which is just a variant of D (or a meshing together of D and B), but may have different pros and cons. I like this conceptually: No `WrapL`/`WrapX`/`XWrap`/`XRec` (the trouble to find a fitting name already suggests that it's maybe a little too general a conc

Re: Handling source locations in HsSyn via TTG

2019-10-30 Thread Spiwack, Arnaud
I would like to submit a solution E, which is just a variant of D (or a meshing together of D and B), but may have different pros and cons. Keep the ping-pong style. But! Let Located take the pass as an argument. Now, Located would be data Located p a = L (XLoc p) a We could define XLoc p to be

users-guide page for master branch

2019-10-30 Thread Takenobu Tani
Hi Ben, devs, This is not in hurry. It looks like the users-guide page for master branch [1] has not been updated recently. [1]: https://ghc.gitlab.haskell.org/ghc/doc/users_guide Regards, Takenobu ___ ghc-devs mailing list ghc-devs@haskell.org http:/

Linking problem

2019-10-30 Thread Simon Peyton Jones via ghc-devs
Devs On the branch wip/inline-compulsory, I'm getting a strange link error: simonpj@MSRC-3645512:~/tmp$ ~/code/HEAD-2/inplace/bin/ghc-stage1 Hello.hs [1 of 1] Compiling Main ( Hello.hs, Hello.o ) Linking Hello ... /home/simonpj/code/HEAD-2/rts/dist/build/libHSrts.a(Updates.o):stg_bh