- ghc-devs - Haskell.org

Kind page of trac wiki
by Takenobu Tani 13 Jan '17

13 Jan '17

Dear devs, May I update Kind page of trac wiki [1] as following ? - "#" is the kind of unboxed values. Things like Int# have kind #. + "#" is the kind of unlifted values. Things like Int# have kind #. Is this correct? (These pages [2][3] are explained as "unlifted values".) [1]: https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/Kinds [2]: https://ghc.haskell.org/trac/ghc/wiki/UnliftedDataTypes [3]: https://ghc.haskell.org/trac/ghc/wiki/NoSubKinds Regards, Takenobu

2 2

Build failures
by Simon Peyton Jones 13 Jan '17

13 Jan '17

recomp001 is failing on Harbormaster on OSX (only). Does anyone know why? See for example https://phabricator.haskell.org/harbormaster/build/18293/ Simon

2 1

ANN: `dump-core` a prettier GHC core viewer
by Iavor Diatchki 13 Jan '17

13 Jan '17

Hello, Over the holidays I wrote a small GHC plugin to help me do some low-level optimizations of Haskell code. I thought it might be of use to other people too, so please try it out! When enabled, the plugin will save the Core generated by GHC in JSON format, and also render it in HTML for human inspection. The plugin is available on Hackage: http://hackage.haskell.org/package/dump-core The instructions on how to use it are in the README file. You may also read about it at the github page: http://hackage.haskell.org/package/dump-core There are many things that could probably be improved, just let me know. Also, if you are good at design, I could use some help making things look prettier :) Happy hacking, -Iavor

6 7

Inlining Wiki Page
by Matthew Pickering 12 Jan '17

12 Jan '17

Dear Devs, I've spent the last day looking at the inliner. In doing so I updated the wiki page about inlining to be a lot more useful to other people wanting to understand the intricacies and problems. https://ghc.haskell.org/trac/ghc/wiki/Inlining This looks like the perfect place for a newcomer to start working on GHC. The inliner is quite well contained, there are lots of open tickets with well-specified aims and lots of investigatory work to be done. So the purpose of this email is: 1. Please tag any tickets relevant to inlining/specialisation with "Inlining" 2. Any newcomers keen to get involved should read the wiki page and see if they can tackle one of the tickets there. Matt

3 3

many haskell's mails are detected as spam on gmail
by Takenobu Tani 12 Jan '17

12 Jan '17

Hi, I'm using gmail. Recently, many haskell's mails are detected as spam on gmail. (ghc-devs, haskell-cafe, ghc-commit, ...) Does anyone know why? Do you know the workaround? Regards, Takenobu

5 4

Trac to Phabricator (Maniphest) migration prototype
by Matthew Pickering 11 Jan '17

11 Jan '17

Dear devs, I have completed writing a migration which moves tickets from trac to phabricator. The conversion is essentially lossless. The trac transaction history is replayed which means all events are transferred with their original authors and timestamps. I welcome comments on the work I have done so far, especially bugs as I have definitely not looked at all 12000 tickets. http://ec2-52-213-249-242.eu-west-1.compute.amazonaws.com All the user accounts are automatically generated. If you want to see the tracker from your perspective then send me an email or ping me on IRC and I can set the password of the relevant account. NOTE: This is not a decision, the existence of this prototype is to show that the migration is feasible in a satisfactory way and to remove hypothetical arguments from the discussion. I must also thank Dan Palmer and Herbert who helped me along the way. Dan was responsible for the first implementation and setting up much of the infrastructure at the Haskell Exchange hackathon in October. We extensively used the API bindings which Herbert had been working on. Further information below! Matt ===================================================================== Reasons ====== Why this change? The main argument is consolidation. Having many different services is confusing for new and old contributors. Phabricator has proved effective as a code review tool. It is modern and actively developed with a powerful feature set which we currently only use a small fraction of. Trac is showing signs of its age. It is old and slow, users regularly lose comments through accidently refreshing their browser. Further to this, the integration with other services is quite poor. Commits do not close tickets which mention them and the only link to commits is a comment. Querying the tickets is also quite difficult, I usually resort to using google search or my emails to find the relevant ticket. Why is Phabricator better? ==================== Through learning more about Phabricator, there are many small things that I think it does better which will improve the usability of the issue tracker. I will list a few but I urge you to try it out. * Commits which mention ticket numbers are currently posted as trac comments. There is better integration in phabricator as linking to commits has first-class support. * Links with differentials are also more direct than the current custom field which means you must update two places when posting a differential. * Fields are verified so that mispelling user names is not possible (see #12623 where Ben mispelled his name for example) * This is also true for projects and other fields. Inspecting these fields on trac you will find that the formatting on each ticket is often quite different. * Keywords are much more useful as the set of used keywords is discoverable. * Related tickets are much more substantial as the status of related tickets is reflected to parent ticket. (http://ec2-52-213-249-242.eu-west-1.compute.amazonaws.com/T7724) Implementation ============ Keywords are implemented as projects. A project is a combination of a tag which can be used with any Phabricator object, a workboard to organise tasks and a group of people who care about the topic. Not all keywords are migrated. Only keywords with at least 5 tickets were added to avoid lots of useless projects. The state of keywords is still a bit unsatisfactory but I wanted to take this chance to clean them up. Custom fields such as architecture and OS are replaced by *projects* just like keywords. This has the same advantage as other projects. Users can be subscribed to projects and receive emails when new tickets are tagged with a project. The large majority of tickets have very little additional metadata set. I also implemented these as custom fields but found the the result to be less satisfactory. Some users who have trac accounts do not have phab accounts. Fortunately it is easy to create new user accounts for these users which have empty passwords which can be recovered by the appropriate email address. This means tickets can be properly attributed in the migration. The ticket numbers are maintained. I still advocate moving the infrastructure tickets in order to maintain this mapping. Especially as there has been little activity in thr the last year. Tickets are linked to the relevant commits, differentials and other tickets. There are 3000 dummy differentials which are used to test that the linking works correctly. Of course with real data, the proper differential would be linked.(http://ec2-52-213-249-242.eu-west-1.compute.amazonaws.com/T11044) There are a couple of issues currently with the migration. There are a few issues in the parser which converts trac markup to remarkup. Most comments have very simple with just paragraphs and code blocks but complex items like lists are sometimes parsed incorrectly. Definition lists are converted to tables as there are no equivalent in remarkup. Trac ticket links are converted to phab ticket links. The ideal time to migrate is before the end of January The busiest time for the issue tracker is before and after a new major release. With 8.2 planned for around April this gives the transition a few months to settle. We can close the trac issue tracker and continue to serve it or preferably redirect users to the new ticket. I don't plan to migrate the wiki at this stage as I do not feel that the parser is robust enough although there are now few other technical challenges blocking this direction.

8 25

Pattern checker status
by David Feuer 11 Jan '17

11 Jan '17

Could you possibly give us an update about the current status of your pattern checker work? I know the number of tickets may seem a bit overwhelming; please reach out to the ghc-devs list, or individual developers, to get whatever help you need. Knocking out some of these tickets is a priority for 8.2, and the freeze is coming up fast. In my mind, the top priorities for GHC 8.2 should probably be #10746 and #12949. We really want to get those squashed. I think #11195 is also a fairly high priority (if it's still an issue!). #10746 is a serious correctness issue, and Simon's suggested fix sounds straightforward. Have you run into trouble? #12949 is also a serious correctness issue. You're right that desugaring doesn't happen till after type checking, but I believe the type checker should have already worked out what it needs to be able to desugar the overloading. It would be worth asking how you might access that information. #11195 looks like a practically important and serious performance problem. I know you spent some time investigating it months ago; do you have any more recent progress to report? Do you know if the problem is still there? David Feuer

1 0

nofib on Shake
by Michal Terepeta 10 Jan '17

10 Jan '17

Hi all, While looking at nofib, I've found a blog post from Neil Mitchell [1], which describes a Shake build system for nofib. The comments mentioned that this should get merged, but it seems that nothing actually happened? Is there some fundamental reason for that? If not, I'd be interested picking this up - the current make-based system is pretty confusing for me and `runstdtest` looks simply terrifying ;-) We could also create a cabal and stack files for `nofib-analyse` (making it possible to use some libraries for it). Thanks, Michal [1] http://neilmitchell.blogspot.ch/2013/02/a-nofib-build-system-using-shake.ht…

4 8

Debugging GHC with GHCi
by Thomas Jakway 10 Jan '17

10 Jan '17

I want to be able to load certain GHC modules in interpreted mode in ghci so I can set breakpoints in them. I have tests in the testsuite that are compiled by inplace/bin/ghc-stage2 with -package ghc. I can load the tests with ghc-stage2 --interactive -package ghc but since ghc is compiled I can only set breakpoints in the tests themselves. Loading the relevant files by passing them as absolute paths to :l loads them but ghci doesn't stop at the breakpoints placed in them (I'm guessing because ghci doesn't realize that the module I just loaded is meant to replace the compiled version in -package ghc). So if I use inplace/bin/ghc-stage2 --interactive -package ghc mytest.hs then :l abs/path/to/AsmCodeGen.hs and set breakpoints, nothing happens. Ideally I'd only have to load the module I'm debugging (and it's dependencies?) but if that isn't possible how would I get ghci to load all of GHC in interpreted mode (intead of using -package ghc)? Currently I'm using trace & friends to do printf-style debugging but it's definitely not ideal. -Thomas Jakway

5 5

GHC 8.2.1 tree freeze timing
by Ben Gamari 10 Jan '17

10 Jan '17

tl;dr. The feature freeze for GHC 8.2 will happen on 30 January 2016. Get any patches you'd like to see in 8.2 up on Phabricator soon! Hello everyone, GHC 8.2.1 is quickly approaching. Our plan is to do a release candidate in February, so we would like to have the tree sorted out by the end of this month. Consequently, I would like to set a general feature freeze for 30 Janary 2016. After the freeze I will be much less likely to accept larger patches; ideally all work post-freeze should be in the name of preparing the tree for cutting the ghc-8.2 branch. If you are concerned that your work isn't positioned to meet this freeze date then please speak to me so we can make appropriate arrangements. Happy hacking! Cheers, - Ben

1 0