November 2014 - ghc-devs

let app invariant failure, HALP Re: how to write a ghc primop that acts on an unevaluated argument?
by Carter Schonwald 27 Nov '14

27 Nov '14

ok, i'm getting a let/app invariant failure when i build my test case with O1 or O2 but not without http://lpaste.net/114881 any help would be appreciated on how to address that On Sun, Nov 23, 2014 at 4:13 PM, Carter Schonwald < carter.schonwald(a)gmail.com> wrote: > yup, i have that! > > wrapFetch prefetchValue0# (error "this shouldn't get evaluated") > > in the test suite! > > in contrast > wrapFetch prefetchValue0# $! (error "this shouldn't get evaluated") > does explode > > shall I add a "should fail" test with the latter? (it doesn't seem > worthwhile) > > On Sun, Nov 23, 2014 at 3:53 PM, Edward Kmett <ekmett(a)gmail.com> wrote: > >> Maybe test for laziness in the argument by just putting something in that >> goes boom when forced, e.g. 'undefined'? >> >> >> On Sun, Nov 23, 2014 at 2:04 PM, Carter Schonwald < >> carter.schonwald(a)gmail.com> wrote: >> >>> Hey All, >>> as part of trying to get some fixups for how prefetch works into 7.10, >>> i'm adding a "prefetchValue" primop that prefetchs the memory location >>> of a lifted heap value >>> >>> namely >>> >>> several operations of the following form >>> >>> primop PrefetchValueOp1 "prefetchValue1#" GenPrimOp >>> a -> State# s -> State# s >>> with strictness = { \ _arity -> mkClosedStrictSig [botDmd, topDmd] >>> topRes } >>> >>> I'd like some feedback on the strictness information design by someone >>> who's familiar with how that piece of GHC. the idea being that >>> prefetchValue is lazy in its polymorphic argument (it doesn't force it, it >>> just does a prefetch on the heap location, which may or may not be >>> evaluated). >>> >>> https://phabricator.haskell.org/D350 >>> >>> is the code in question. And i *believe* i'm testing for being lazy in >>> that argument correctly. >>> >>> thoughts? >>> >>> many thanks! >>> -Carter >>> >>> >>> _______________________________________________ >>> ghc-devs mailing list >>> ghc-devs(a)haskell.org >>> http://www.haskell.org/mailman/listinfo/ghc-devs >>> >>> >> >

2 9

superfluous ghc --make log?
by Tuncer Ayaz 27 Nov '14

27 Nov '14

This is a very minor "issue", but I've been wondering if there's a rationale behind ghc --make pretty much printing the same thing thrice. Say you're building Cabal, you'll see (line wrapped for email): [ 1 of 75] Compiling Distribution.Compat.CreatePipe ( Distribution/Compat/CreatePipe.hs, Distribution/Compat/CreatePipe.o ) So, why not print [ 1 of 75] Compiling Distribution.Compat.CreatePipe instead? I'm assuming there's a good reason for the current behavior, but if there's none, are there any objections to changing what's printed? Of course, the old behavior could be re-enabled via -v.

2 1

Uploading a patch (without arcanist)
by Tuncer Ayaz 26 Nov '14

26 Nov '14

When trying to upload a diff with Differential's web interface, all I see is the following error message: --------snip-------- Unhandled Exception ("PhabricatorApplicationTransactionNoEffectException") Transactions have no effect: - This Revision already has that view policy. --------snip-------- Any idea what I might have done wrong?

2 1

T5462Yes1
by Simon Peyton Jones 26 Nov '14

26 Nov '14

I'm getting this on Linux: Unexpected failures: generics T5462Yes1 [exit code non-0] (normal) Linking T5462Yes1 ... gcc: error: GEq/GEq1A.o: No such file or directory gcc: error: GFunctor/GFunctor.o: No such file or directory *** unexpected failure for T5462Yes1(normal) But it doesn't happen if I say "make TEST=T5462Yes1". Could this be a multi-thread file deletion thing? make TEST=T5462Yes1 runs the test 8 different ways Simon

2 4

ghc HEAD can't validate with xcode 6 clang on OS X
by Carter Schonwald 26 Nov '14

26 Nov '14

Hey all, on OS X 10.9 if i do git clone --recursive git://git.haskell.org/ghc.git ghc-valifail cd ghc-valifail perl boot ./configure --with-gcc=clang # the with gcc bit isnt needed, but making it clearly pick up clang is the point ./validate --fast then within a minute or two i get error: unknown warning option '-Werror=unused-but-set-variable'; did you mean '-Werror=unused-const-variable'? [-Werror,-Wunknown-warning-option] which makes me think that the clang warning flags have changed in that release (which corresponds with clang Apple LLVM version 6.0 (clang-600.0.54) (based on LLVM 3.5svn)). SO maybe clang 3.5 / 3.6 will also fail when used in validate builds? s/hpc/dist-boot/build/autogen/cabal_macros.h libraries/hpc/./Trace/Hpc/Reflect.hsc -o libraries/hpc/dist-boot/build/Trace/Hpc/Reflect.hs error: unknown warning option '-Werror=unused-but-set-variable'; did you mean '-Werror=unused-const-variable'? [-Werror,-Wunknown-warning-option] compiling compiler/stage1/build/Fingerprint_hsc_make.c failed (exit code 1) command was: clang -c compiler/stage1/build/Fingerprint_hsc_make.c -o compiler/stage1/build/Fingerprint_hsc_make.o -Werror -Wall -m64 -fno-stack-protector -m64 -Dx86_64_HOST_ARCH=1 -Ddarwin_HOST_OS=1 -D__GLASGOW_HASKELL__=708 -m64 -fno-stack-protector -error: unknown warning option '-Werror=unused-but-set-variable'; did you mean '-Werror=unused-const-variable'? [-Werror,-Wunknown-warning-option] Werror -Wall -Icompiler/. -Icompiler/parser -Icompiler/utils -Icompiler/stage1 -isystem/usr/local/lib/ghc-7.8.3/process-1.2.0.0/include -isystem/usr/local/lib/ghc-7.8.3/directory-1.2.1.0/include -isystem/usr/local/lib/ghc-7.8.3/unix-2.7.0.1/include -isystem/usr/local/lib/ghc-7.8.3/time-1.4.2/include -isystem/usr/loccalo/mlpiibl/ignhgc -l7i.b8r.a3r/ibeyst/ehsptc/dist-boot/build/Trace/Hpc/Reflect_hsc_make.c fring-0.10.4.0/include -isystemailed (exit c/usr/local/liode 1) commab/ghc-7.8.3/band was: clanse-4.7.0.1/ing -c librariclude -isystees/hpc/dist-m/usr/localboot/build/T/lib/ghc-7.8race/Hpc/Ref.3/inlteecgte_rh-sgcm_pm-a0k.e5.1.0/include -isys.c -o libraries/hpc/dist-boott/bueiml/du/sTrr/acel/Hopcca/l/lib/ghc-7.8.3/include -Werror=unused-but-sReet-variabflel e-Wcnto_-hesrcr_omra=kien.loi n-eW e-rIrcoorm p-iWlaelrl/ s-tma6g4e 1-/fbnuoi-lsdt/aacukt-opgreont e-citnocrl u-dme6 4c o-mDpxi8l6e_r6/4s_tHaOgSeT1_/AbRuCiHl=d1/ a-uDtdoagrewni/nc_aHbOaSlT__mOaSc=r1o s-.Dh_ _-GIL/AUSsGeOrWs_/HcAaSrKtEeLrL/_D_e=s7k0t8o p-/mr6e4p o-Sfcnor-asttcahcekr-/pgrhoct-evcatloirf a-iWle/rirnoprl a-cWea/llli b-/Iilnicblrudaer/i es/hpc/. -isystem/usr/local/lib/ghc-7.8.3/directory-1.2.1.0/include -isystem/usr/local/lib/ghc-7.8.3/unix-2.7.0.1/include -isystem/usr/local/lib/ghc-7.8.3/time-1.4.2/include -isystem/usr/local/lib/ghc-7.8.3/bytestring-0.10.4.0/include -isystem/usr/local/lib/ghc-7.8.3/base-4.7.0.1/include -isystem/usr/local/lib/ghc-7.8.3/integer-gmp-0.5.1.0/include -isystem/usr/local/lib/ghc-7.8.3/include -Werror=unused-but-set-variable -Wno-error=inline -Ilibraries/hpc/dist-boot/build/autogen -include libraries/hpc/dist-boot/build/amake[1]: *** [compiler/stage1/build/Fingerprint.hs] Error 1 make[1]: *** Waiting for unfinished jobs.... utogen/cabal_macros.h -I/Users/carter/Desktop/repoScratcher/ghc-valifail/inplace/lib/include/ make[1]: *** [libraries/hpc/dist-boot/build/Trace/Hpc/Reflect.hs] Error 1 make: *** [all] Error 2

2 1

More flexible literate Haskell extensions (Trac #9789), summary on wiki
by Merijn Verstraaten 25 Nov '14

25 Nov '14

As requested on my ticket I summarised the entire proposal on the wiki here: https://ghc.haskell.org/trac/ghc/wiki/FlexibleLiterateExtension I don't expect a lot of disagreement on discussion, aside from minor bike shedding on the flavour of the extension. I've started implementing this already. I'm open to bikesheds on exact extension, as it shouldn't affect the implementation. Unless there's any vehement objections, I'll produce a diff on fabricator asap. Cheers, Merijn

8 11

NOTE: The STABLE freeze is scheduled to occur TODAY.
by Austin Seipp 25 Nov '14

25 Nov '14

Hi friends, Today, I'm planning on trying to cut a new `ghc-7.10` branch for the stable freeze. That means I'm going to spend a lot of time merging patches and other things with several other developers because everything is crazy and so many things wow. If you have things you want me to review, then please: - Talk to me on IRC, #ghc on Freenode (I am 'thoughtpolice') - Ping me on some medium like Skype (search for me). We can schedule a chat for a short time to figure things out. - I can also do something like G+ or whatnot. - I will of course be reading my email. Please note I would actually prefer to stay *away* from email I think, since it's a larger context switch for me, but I'll actively check it still just in case you want something and need to explain it. I'll likely be doing this most of the day, so let me know what happens. -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

3 4

has anyone tested the llvm backend changes on OS X yet?
by Carter Schonwald 25 Nov '14

25 Nov '14

i'm trying to test out the llvm backend on OS X with ghc head plus llvm 3.5 and i'm seeing stuff like the following. Could someone help me undestand whats going on?! 2 <http://lpaste.net/115021#line2>3 <http://lpaste.net/115021#line3>4 <http://lpaste.net/115021#line4>5 <http://lpaste.net/115021#line5>6 <http://lpaste.net/115021#line6>7 <http://lpaste.net/115021#line7>8 <http://lpaste.net/115021#line8>9 <http://lpaste.net/115021#line9>10 <http://lpaste.net/115021#line10>11 <http://lpaste.net/115021#line11> *** Clang (Assembler):clang -m64 -fno-stack-protector -DTABLES_NEXT_TO_CODE -I. -fno-common -U__PIC__ -D__PIC__ -Qunused-arguments -x assembler -c /var/folders/py/wgp_hj9d2rl3cx48yym_ynj00000gn/T/ghc89553_0/ghc89553_7.s -o TestFetch.o /var/folders/py/wgp_hj9d2rl3cx48yym_ynj00000gn/T/ghc89553_0/ghc89553_7.s:3:2: error: unknown directive .macosx_version_min 10, 0 ^ <no location info>: Error running clang! you need clang installed to use theLLVM backend (or GHC tried to execute clang incorrectly)

1 0

mask in waitQSem
by Yuras Shumovich 25 Nov '14

25 Nov '14

Hello, I was reviewing some exception handling code in base library, and I found this line: https://phabricator.haskell.org/diffusion/GHC/browse/master/libraries/base/… Here mask is used, but I looks completely useless for me. waitQSem itself should be called with async exceptions masked, otherwise there is no way to prevent resource leak. Do anyone know why mask is used here? I wonder whether an author of the code tried to do something different, so there actually can be a bug hidden here. Probably uninterruptibleMask_ should be used here? (I don't think so though.) Thanks, Yuras

3 8

Diff grouping question
by Alan & Kim Zimmerman 24 Nov '14

24 Nov '14

I am picking up some minor updates required for the API annotations, relating to documentation inaccuracies, and some missing annotations needing to be captured in the parser. Should these go into separate Phab diffs, or can I just put them all in one? Alan

2 1