On Tue, Sep 24, 2013 at 6:53 AM, Jan Stolarek wrote:

Austin, will you be able to apply changes from my branch to upstream primitive?

Your patches are based on an outdated version of the library. I just wrote a new patch and applied it. It builds fine on several versions of GHC, so I tagged primitive 0.5.1.0 and released it to Hackage just now.

On Tue, Sep 24, 2013 at 11:47 AM, Jan Stolarek wrote:

That's really surprising - I based them on code available at http://code.haskell.org/primitive, which I believe was version 0.5.0.1. Was there anything newer?

Oh, I was going on the versions that are in a repo on git.haskell.org.

On 9/24/13 6:17 PM, Herbert Valerio Riedel wrote:

Hello Jan,

On 2013-09-24 at 20:47:31 +0200, Jan Stolarek wrote:

...

...

Your patches are based on an outdated version of the library. That's really surprising - I based them on code available at http://code.haskell.org/primitive, which I believe was version 0.5.0.1. Was there anything newer? 0.5.0.1 also matches exactly what our darcs2git mirror repo at

http://git.haskell.org/darcs-mirrors/primitive.git

currently holds; and the GitHub repo has all commits from there (albeit with slightly diverged commit-ids after 0.4.0.1, but that's harmless)

However, I've tried integrating the new vector/primitive versions released into the GHC build (after patching up the DPH libs), but I get Core lint errors:

http://lpaste.net/93354

any idea what's going on here?

Cheers, hvr Hm, #8138? Richard marked that as closed, though.

You didn't try to update the version of vector in the GHC build, did you? Geoff

On 09/25/2013 02:51 AM, Herbert Valerio Riedel wrote:

On 2013-09-25 at 02:40:51 +0200, Geoffrey Mainland wrote:

[...]

...

...

However, I've tried integrating the new vector/primitive versions released into the GHC build (after patching up the DPH libs), but I get Core lint errors:

http://lpaste.net/93354

any idea what's going on here?

...

Hm, #8138? Richard marked that as closed, though.

You didn't try to update the version of vector in the GHC build, did you?

Well, of course I did :-)

but afaics the error occurs already when trying to compile the new 'primitive' by itself...

But you can easily reproduce w/o replacing the 'primitive' used for building GHC HEAD, but simply by trying to build the relased primitive-0.5.1.0 package with GHC HEAD via cabal:

cabal update cabal install --ghc-option=-dcore-lint primitive-0.5.1.0

Looks like #7643. Here's my work-around: https://github.com/mainland/primitive/commit/21fd4d055a26552919d06fbf7433f72... Note that DPH is tied to the old version of vector, so updating vector will not work. I have patches to DPH to get it to compile with the new version of vector, but the DPH folks have plans to re-do the way vectorization is done, so it's probably not worth trying to get my patches included. Geoff

On 2013-09-25 at 05:50:23 +0200, Bryan O'Sullivan wrote:

On Tue, Sep 24, 2013 at 6:17 PM, Herbert Valerio Riedel wrote:

...

However, I've tried integrating the new vector/primitive versions released into the GHC build (after patching up the DPH libs), but I get Core lint errors:

No clue. For me, the new releases of primitive and vector build happily with a version of HEAD that's a day old.

I assume you built primitive/vector normally w/o -dcore-lint, in which case those errors would not be checked for

Hello Jan, On 2013-09-25 at 08:26:15 +0200, Jan Stolarek wrote:

...

However, I've tried integrating the new vector/primitive versions released into the GHC build (after patching up the DPH libs), but I get Core lint errors:

http://lpaste.net/93354

any idea what's going on here?

I have no idea what might be the cause. During my work on new primops I haven't seen anything like this.

Fyi, I tried your primitive-0.5.0.2 version[1] as well, and build that package with cabal configure --ghc-option=-dcore-lint && cabal build which gave me a core-lint error as well; if you have the time, could you please try to reproduce this on your setup? Cheers, hvr [1]: https://github.com/jstolarek/primitive/tree/ghc-78-compatibility