- ghc-devs - Haskell.org

Status updates
by Austin Seipp 06 Jun '14

06 Jun '14

Hello all, A cumulative status update will now appear, to summarize a few things that have happened in the past little while since I've been somewhat absent and short on time. - 7.8.3 is looming, because we have a lot of bugfixes as I said last week: https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8.3 That's nearly 30 tickets axed in the past few weeks since 7.8.2, so not bad! As I said before, I'm eager to release sooner rather than later as my time is short. Do keep weighing in if you have anything to say or want something fixed. Now is really the time! - AMP/ORF - these are still on branches, but me and Simon have gotten hung up on a few things delaying it. They'll go in soon, promise! (For certain definitions of 'soon', cooperating with time schedules). AMP in particular can probably land very, very soon. Otherwise we're past a lot of other churn, like removing external core and whatnot. - I merged a bunch of patches this morning to the 7.8 branch, bringing it close to what I expect we will ship 7.8.3 with. Again, pester me soon if you want something! - There's now a proper CI link for GHC on Trac so people don't lose it. The new builders are checking in regularly, so please watch out for them - and subscribe to ghc-builds(a)haskell.org if you haven't already. - Some other churn in the tree has not yet passed; I still need to improve and land my performance patches for copies, for example. - XCode 5.1 has introduced some other breaking changes I'll need to fix (things *work*, but the testsuite is useless due to the warning spewage), along with merging the remaining patches. - Also, if you have spare hardware, please email Gabor Pali (or just email the list itself, or reply to this thread) if you're willing to donate, that would be awesome. Another Mac OS X target would be especially welcome, I think (my development machine is on loan right now), and I will have better dedicated Windows targets soon. I'll send another email about 7.8.3 shortly. -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

5 6

pushing to haddock
by Simon Peyton Jones 06 Jun '14

06 Jun '14

I'm trying desperately to follow the instructions on https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Git/Submodules for how to update haddock to follow a small change to GHC. I've checked out the haddock master, made my patch, and want to push to haddock. But my push is rejected for an inscrutable reason: git status # On branch master # Your branch is ahead of 'origin/master' by 1 commit. # nothing to commit (working directory clean) simonpj@cam-05-unx:~/code/HEAD-2/utils/haddock$ git push Counting objects: 9, done. Delta compression using up to 32 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 470 bytes, done. Total 5 (delta 4), reused 0 (delta 0) remote: W refs/heads/master haddock simonpj DENIED by refs/.* remote: error: hook declined to update refs/heads/master To ssh://git@ghc.haskell.org/haddock.git ! [remote rejected] HEAD -> master (hook declined) error: failed to push some refs to 'ssh://git@ghc.haskell.org/haddock.git' simonpj@cam-05-unx:~/code/HEAD-2/utils/haddock$ What do I do now? Presumably once that's done I include the change to utils/haddock in my patch to HEAD, correct? Getting to Haddock HEAD added 12 new patches on the haddock branch so I suppose they'll be included too. I don't know whether that is good or bad. help! Simon

2 6

haddock in 7.8.3
by Simon Peyton Jones 06 Jun '14

06 Jun '14

I want to change the interface to PatSyn.patSynSig, as part of fixing a bug in 7.8.2. But Haddock calls patSynSig, so there is a (fairly trivial) knock on change to Haddock Is that acceptable in a 7.8.3 release cycle? If not, I can program round it in the 7.8.3 branch. But if it's not a problem, it'd be a bit easier just to make the change in Haddock? (Really Haddock has to be co-released with GHC, since it depends on many internal GHC details.) Simon

2 1

can a StgRhs have NoCCS when -prof is provided?
by Ömer Sinan Ağacan 05 Jun '14

05 Jun '14

Hi all, Can a StgRhs have `NoCCS` as cost-centre stack when -prof is provided while compiling? Or is it always oneOf [CurrentCCS, DontCareCCS, SingletonCCS]? I presume that since we have CCS constructor "DontCareCCS" and CCS field of StgRhs constructors are not `Maybe CostCentreStack` (so they're not optional), when -prof is provided CCS fields should not be filled with NoCCS(if we still don't care about CCS for some reason, it should be DontCareCCS) but I just wanted to make sure. Thanks. --- Ömer Sinan Ağacan http://osa1.net

2 1

Expose Other Parsers for GHC API
by Andrew Gibiansky 04 Jun '14

04 Jun '14

Hello, I would like to be able to use the GHC API for parsing. Right now this is in the Parser and Lexer modules: Parser: http://www.haskell.org/ghc/docs/7.8.2/html/libraries/ghc-7.8.2/Parser.html Lexer: http://www.haskell.org/ghc/docs/7.8.2/html/libraries/ghc-7.8.2/Lexer.html GHC currently exposes only a few parsers here. I'd like to make a few modifications: 1. Expose a few more parsers than currently are exposed in the Parser module. In particular, I'd like import statements, type signatures, declarations, and expressions, at least, in addition to what's already there. 2. Re-export some things from Lexer from Parser, since they're reused. This would include unP, PState, and the 2-3 other core things you *have* to use in order to use the GHC Parser. 3. Add some Haddock documentation to the top of the Parser module describing how to use it, since the types themselves are pretty opaque here. I think (1) and (3) are definitely a good idea, not so sure about (2) though IMHO it would be convenient for using the Parser. Would this make for an acceptable patch? Thoughts? -- Andrew Gibiansky

3 2

[PATCH] Fix T5435_dyn_asm on mingw and T8832 on 32-bit architecture
by transfuturist 04 Jun '14

04 Jun '14

--- testsuite/tests/rts/all.T | 3 +++ testsuite/tests/simplCore/should_compile/all.T | 3 ++- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/testsuite/tests/rts/all.T b/testsuite/tests/rts/all.T index a56a3f3..c52cea0 100644 --- a/testsuite/tests/rts/all.T +++ b/testsuite/tests/rts/all.T @@ -141,6 +141,9 @@ def checkDynAsm(actual_file, normaliser): elif actual == ['ctors1', 'ctors2', 'initArray1', 'initArray2', 'success']: if_verbose(1, 'T5435_dyn_asm detected old-style dlopen, see #8458') return 1 + elif opsys('mingw32'): + if actual == ['ctors1', 'ctors2', 'success']: + return 1 else: if_verbose(1, 'T5435_dyn_asm failed with %s, see all.T for details' % actual) return 0 diff --git a/testsuite/tests/simplCore/should_compile/all.T b/testsuite/tests/simplCore/should_compile/all.T index 616b6cc..ffc7131 100644 --- a/testsuite/tests/simplCore/should_compile/all.T +++ b/testsuite/tests/simplCore/should_compile/all.T @@ -198,7 +198,8 @@ test('T5996', ['$MAKE -s --no-print-directory T5996']) test('T8537', normal, compile, ['']) test('T8832', - extra_clean(['T8832.hi', 'T8832a.o']), + [extra_clean(['T8832.hi', 'T8832a.o']), + when(wordsize(32),expect_broken(8832))], run_command, ['$MAKE -s --no-print-directory T8832']) test('T8848', only_ways(['optasm']), compile, ['-ddump-rule-firings']) -- 1.8.4.msysgit.0

2 1

Validate failures
by Joachim Breitner 03 Jun '14

03 Jun '14

Hi, I’m seeing these failures on travis. Anyone feeling responsible? master: Actual stderr output differs from expected: --- /dev/null 2014-05-03 18:30:46.325826237 +0000 +++ ./ffi/should_compile/cc004.comp.stderr 2014-05-03 19:08:47.864969234 +0000 @@ -0,0 +1,73 @@ + +cc004.hs:16:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "static p" m_stdcall + :: StablePtr a -> IO (StablePtr b) + +cc004.hs:21:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "static my_sin" my_sin + :: Double -> IO Double + +cc004.hs:22:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "static my_cos" my_cos + :: Double -> IO Double + +cc004.hs:24:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "static m1" m8 :: IO Int8 + +cc004.hs:25:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "static m2" m16 :: IO Int16 + +cc004.hs:26:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "static m3" m32 :: IO Int32 + +cc004.hs:27:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "static m4" m64 :: IO Int64 + +cc004.hs:29:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "dynamic" d8 + :: FunPtr (IO Int8) -> IO Int8 + +cc004.hs:30:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "dynamic" d16 + :: FunPtr (IO Int16) -> IO Int16 + +cc004.hs:31:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "dynamic" d32 + :: FunPtr (IO Int32) -> IO Int32 + +cc004.hs:32:1: Warning: + the 'stdcall' calling convention is unsupported on this platform, + treating as ccall + When checking declaration: + foreign import stdcall safe "dynamic" d64 + :: FunPtr (IO Int64) -> IO Int64 *** unexpected failure for cc004(normal) and Wrong exit code (expected 0 , actual 1 ) Stdout: Stderr: cgrun051: OK *** unexpected failure for cgrun051(normal) (https://s3.amazonaws.com/archive.travis-ci.org/jobs/24347514/log.txt) ghc-7.8: Unexpected failures: annotations/should_compile/th annth_compunits [bad exit code] (normal) annotations/should_compile/th annth_make [bad stdout] (normal) Please merge 0fe726829d468badf830dd82bc296832d709733b into ghc-7.8 (this annotates the tests to require have_dynamic()) Greetings, Joachim -- Joachim “nomeata” Breitner mail(a)joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata(a)joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata(a)debian.org

3 5

Ptr type
by Simon Peyton Jones 03 Jun '14

03 Jun '14

Richard In GHC.Ptr we see type role Ptr representational data Ptr a = Ptr Addr# deriving (Eq, Ord) with no comments. Why is Ptr representational? In the same module we have castPtr, which unpacks and repacks a Ptr. If Ptr was phantom, we could use coerce. And that in turn would actually make a lot of code more efficient - there are lots of calls to castPtr. Simon

3 3

suspicious piece of code in RTS(Profiling.c) code
by Ömer Sinan Ağacan 03 Jun '14

03 Jun '14

Hi all, I recently found a suspicious piece of code in RTS code. * https://github.com/ghc/ghc/blob/master/rts/Profiling.c#L622 here it's checking that ccs is not EMPTY_STACK. * https://github.com/ghc/ghc/blob/master/includes/rts/prof/CCS.h#L96 here EMPTY_STACK is defined as NULL. Now weird part is that before the if-statement checks for `ccs != NULL` ccs is used to reach some of it's fields(for example, line 601 and 602). As far as I can see either we have a bug here or the if-statement is not necessary and we can move it's body to top level. Am I missing anything here? Thanks. --- Ömer Sinan Ağacan http://osa1.net

3 2

32-bit OSX
by Edsko de Vries 01 Jun '14

01 Jun '14

Hi guys, I have been trying to compile a 32-bit version ghc, versions 7.8 as well as HEAD, in a myriad of ways, bootstrapping with the 32-bit binary of 7.4 (which is the latest 32-bit binary available from haskell.org) but no matter which way I try, it always fails somewhere. I was trying this mostly just because I wanted to inspect the output of the code generator, but 32-bit OSX is listed as a tier 1 platform on https://ghc.haskell.org/trac/ghc/wiki/Platforms, so I expected this to be simple. Compiling normally (build flavour quick) eventually fails with a bus error, which somebody else seems to have got too -- although I have no idea who or what there were trying to do; I just found http://lpaste.net/99008 When I try to build with the quick-cross flavour, but using -fasm rather than -fllvm, for some reason building fails when it tries to call ghc-stage2; the quick-cross flavour sets Stage1Only = YES so this seems a bug to me. When using -fllvm it fails even sooner. I don't know if I'm doing this wrong, if I should file a bug, or whether we should record 32-bit OSX as unsupported. Edsko

1 0