Re: Folding ghc/testsuite repos *now*, 2nd attempt (was: Repository Reorganization Question)

2014-01-10 Thread Austin Seipp
+1 from me as well. On Thu, Jan 9, 2014 at 4:31 AM, Herbert Valerio Riedel wrote: > Hello All, > > It seems to me, there were no major obstacles left unaddressed in the > previous discussion[1] (see summary below) to merging testsuite.git into > ghc.git. > > So here's one last attempt to get test

Re: Validating with Haddock

2014-01-10 Thread Mateusz Kowalczyk
On 10/01/14 10:01, Mateusz Kowalczyk wrote: > Hi all, > > I have now merged in the new parser and new features onto a single > branch. I'm having some issues validating with HEAD at the moment > (#8661, unrelated problem) but while I get that sorted out, someone > might want to try validating with

Re: High-level Cmm code and stack allocation

2014-01-10 Thread Simon Marlow
So stack areas are still a great abstraction, the only change is that they now overlap. It's not just about stack getting too big, I've copied the notes I made about it below (which I will paste into the code in due course). The nice property that we can generate well-defined Cmm without know

RE: High-level Cmm code and stack allocation

2014-01-10 Thread Simon Peyton Jones
Oh, ok. Alas, a good chunk of my model of Cmm has just gone out of the window. I thought that areas were such a lovely, well-behaved abstraction. I was thrilled when we came up with them, and I'm very sorry to see them go. There are no many things that I no longer understand. I now have no i

Re: High-level Cmm code and stack allocation

2014-01-10 Thread Simon Marlow
There are no one-slot areas any more, I ditched those when I rewrote the stack allocator. There is only ever one live area: either the old area or the young area for a call we are about to make or have just made. (see the data type: I removed the one-slot areas) I struggled for a long time wi

RE: High-level Cmm code and stack allocation

2014-01-10 Thread Simon Peyton Jones
That documentation would be good, yes! I don't know what it means to say "we don't really have a general concept of areas any more". We did before, and I didn't know that it had gone away. Urk! We can have lots of live areas, notably the old area (for the current call/return parameters, the

Re: Changing GHC Error Message Wrapping

2014-01-10 Thread Andrew Gibiansky
Thanks! On Fri, Jan 10, 2014 at 9:21 AM, Simon Peyton Jones wrote: > Crumbs. You are absolutely right. I’ll fix that. (It’s a relic from > when the flags weren’t available to the show functions.) > > > > Simon > > > > *From:* Andrew Gibiansky [mailto:andrew.gibian...@gmail.com] > *Sent:* 08 J

RE: Changing GHC Error Message Wrapping

2014-01-10 Thread Simon Peyton Jones
Crumbs. You are absolutely right. I'll fix that. (It's a relic from when the flags weren't available to the show functions.) Simon From: Andrew Gibiansky [mailto:andrew.gibian...@gmail.com] Sent: 08 January 2014 17:23 To: Simon Peyton Jones Cc: Erik de Castro Lopo; ghc-devs@haskell.org Subject

Re: Validating with Haddock

2014-01-10 Thread Mateusz Kowalczyk
Hi all, I have now merged in the new parser and new features onto a single branch. I'm having some issues validating with HEAD at the moment (#8661, unrelated problem) but while I get that sorted out, someone might want to try validating with Haddock changes on their own platform. The full branch