submodule repos on GitHub

2018-07-17 Thread Richard Eisenberg
Hi devs, The Newcomers page (https://ghc.haskell.org/trac/ghc/wiki/Newcomers) recommends cloning GHC with > git clone --recursive git://github.com/ghc/ghc I believe my students did this with success several weeks ago. But trying it again today leads to trouble with some submodules, e.g.: >

RE: Cmm learning tools

2018-07-17 Thread Simon Peyton Jones via ghc-devs
Here’s a little bit of background. * C—started when Norman Ramsey and I decided to have a stab at designing a “portable assembly language”. * Our primary motivation was GHC: I wanted to clearly separate the business of turning lambda calculus into an imperative language, from that of

Re: submodule repos on GitHub

2018-07-17 Thread Matthew Pickering
Did you do the line above as well? ``` git config --global url."git://github.com/ghc/packages-".insteadOf git://github.com/ghc/packages/ ``` On Tue, Jul 17, 2018 at 8:09 PM, Richard Eisenberg wrote: > Hi devs, > > The Newcomers page (https://ghc.haskell.org/trac/ghc/wiki/Newcomers) >

Re: submodule repos on GitHub

2018-07-17 Thread Artem Pelenitsyn
The other page https://ghc.haskell.org/trac/ghc/wiki/Building/GettingTheSources suggests: git clone --recursive git://git.haskell.org/ghc.git This always works to me. -- Best wishes, Artem вт, 17 июля 2018 г. в 21:14, Matthew Pickering : > Did you do the line above as well? > > ``` > git

Re: submodule repos on GitHub

2018-07-17 Thread Richard Eisenberg
How clever of someone to note that. I stand down. Thanks! > On Jul 17, 2018, at 5:08 PM, Matthew Pickering > wrote: > > It was changed when a large number of people were cloning the > git.haskell.org repo after being posted on reddit and it was causing > load issues. > > There is a comment to

Re: submodule repos on GitHub

2018-07-17 Thread Richard Eisenberg
Aha. I had just jumped to the chase. But is there a reason we don't just point everyone (including newcomers) to git://git.haskell.org/ghc.git ? That's what I always use myself, and it seems simpler to do so. Richard > On Jul 17, 2018, at 3:14 PM, Matthew Pickering > wrote: > > Did you do

Write barrier for stack updates?

2018-07-17 Thread Ömer Sinan Ağacan
Hi Simon, I'm a bit confused about stack updates in generated code and write barriers. Because stacks are mutable (we push new stuff or maybe even update existing frames?) it seems to me that we need one these two, similar to other mutable objects: - Always keep all stacks in mut_lists - Add

Re: submodule repos on GitHub

2018-07-17 Thread Matthew Pickering
It was changed when a large number of people were cloning the git.haskell.org repo after being posted on reddit and it was causing load issues. There is a comment to this effect in the newcomers page source. {{{#!comment -- Note: when this page got mentioned on reddit, git.haskell.org couldn't

Re: Cmm learning tools

2018-07-17 Thread Daniel Cartwright
Thank you, that was very illuminating. On Tue, Jul 17, 2018, 3:37 PM Simon Peyton Jones wrote: > Here’s a little bit of background. > > > >- C—started when Norman Ramsey and I decided to have a stab at >designing a “portable assembly language”. >- Our primary motivation was GHC: I

Re: submodule repos on GitHub

2018-07-17 Thread Artem Pelenitsyn
I personally consider this to be most reasonable. But maybe I oversee something… -- Best, Artem вт, 17 июля 2018 г. в 22:59, Richard Eisenberg : > Aha. I had just jumped to the chase. > > But is there a reason we don't just point everyone (including newcomers) > to git://git.haskell.org/ghc.git

Re: Cmm learning tools

2018-07-17 Thread Gabor Greif
No worries! I searched for C--, which was its name back in the day. There are a bunch of other conference papers in the "GHC commentary" too. Cheers, Gabor Em ter, 17 de jul de 2018 às 08:00, Daniel Cartwright escreveu: > Thanks, I'll check it out. > > P.S.: Apologies if my request