Re: nofib comparisons between 7.0.4, 7.4.2, 7.6.1, and 7.6.2

I'm +1 for this. Eyal Lotem and I were just discussing this on IRC a few minutes ago, and he suffered a rather large (~25%) performance hit when upgrading to 7.6.1, which is unfortunate. Committers are typically very good about recording nofib results in their commit and being performance-courteou

Re: simd branch ready for review

I'm noticing that linked paper (very nice results!) mentions a prefetch primops that were added to ghc. Is there any documentation current or pending ? https://github.com/mainland/vector/commit/cfce37d3a9c228fe4bdf627ffb777399f54af5e5#Data/Vectorseems to have the relevant prim ops mentioned in the

Re: simd branch ready for review

On 02/04/2013 11:56 PM, Johan Tibell wrote: > On Mon, Feb 4, 2013 at 3:19 PM, Geoffrey Mainland > wrote: > > What would a sensible fallback be for AVX instructions? What should we > fall back on when the LLVM backend is not being used? > > Depends on the instruction. A 256-bit multiply could be r

Re: simd branch ready for review

On Mon, Feb 4, 2013 at 3:19 PM, Geoffrey Mainland wrote: > What would a sensible fallback be for AVX instructions? What should we > fall back on when the LLVM backend is not being used? > Depends on the instruction. A 256-bit multiply could be replaced by N multiplies etc. For popcount we have a

Re: simd branch ready for review

On 02/04/2013 10:12 PM, Johan Tibell wrote: > On Mon, Feb 4, 2013 at 2:09 PM, Geoffrey Mainland > wrote: > > I'd like to figure out how to properly support having the set of > available primops depend on the dynamic flags before adding too much > more. I'll be speaking to Simon PJ about it tomorr

nofib comparisons between 7.0.4, 7.4.2, 7.6.1, and 7.6.2

Hi all, I haven't had much time to do performance tzar work yet, but I did run nofib on the last few GHC releases to see the current trend. The benchmarks where run on my 64-bit Core i7-3770 @ 3.40GHz Linux machine. Here are the results: 7.0.4 to 7.4.2: --

Re: simd branch ready for review

1) Awesome 2) Got it, yeah that piece is important. I just took some time to look through whats currently in (on the wiki at http://hackage.haskell.org/trac/ghc/wiki/SIMD/Design) and It looks like for now that'll cover my immediate needs quite nicely! (I have a reflex to jump towards "ALL the

Re: simd branch ready for review

On Mon, Feb 4, 2013 at 2:09 PM, Geoffrey Mainland wrote: > I'd like to figure out how to properly support having the set of > available primops depend on the dynamic flags before adding too much > more. I'll be speaking to Simon PJ about it tomorrow. Could we use a fallback, like we did for e.g.

Re: simd branch ready for review

On 02/04/2013 09:34 PM, Carter Schonwald wrote: > I'm really excited to see this merged in! Props on all involved > > question 1: Will this be included in the upcoming 7.8 release? Yes, that's the plan! > question 2: I see that some of the useful (albeit specialized) SSE > primops aren't included

Re: simd branch ready for review

I'm really excited to see this merged in! Props on all involved *question 1*: Will this be included in the upcoming 7.8 release? *question 2*: I see that some of the useful (albeit specialized) SSE primops aren't included, though it looks like adding them (at least for platforms that support them

Re: links to diffs on ghc-commit emails seem to be broken

I believe Ian disabled the Git integration features of Trac recently as the machine running it has been acting up. Not sure when this will be re-enable, potentially not until we move to a new machine. Cheers, David On 4 February 2013 12:36, Carter Schonwald wrote: > Hey all, > links seem to not

Re: Git confusion

On Mon, Feb 04, 2013 at 07:12:19PM +, Ian Lynagh wrote: > > So having done "git remote rm origin", how do I configure the git pull > branches again? Looks like this does it: git remote add origin darcs.haskell.org:/srv/darcs/ghc.git git fetch origin git branch --set-upstream master origin/ma

links to diffs on ghc-commit emails seem to be broken

Hey all, links seem to not work, though they are included in the emails eg from the email [commit: ghc] master: Move AsmCodeGen.makeFarBranches to PPC.Instr (#709) (aa1d7d3) http://hackage.haskell.org/trac/ghc/changeset/aa1d7d35ac27625c9aa67fe71c186f79600f0201 *should* these be broken or is somet

Re: Git confusion

On Mon, Feb 4, 2013 at 11:12 AM, Ian Lynagh wrote: > > Hi all, > > If I do > git clone darcs.haskell.org:/srv/darcs/ghc.git > cd ghc > git show origin > then the output is > [...] > Local branch configured for 'git pull': > master merges with remote master > [...] >

Re: Git confusion

You can you -t when creating a branch to do what you want. Or for an existing branch you can do it manually. i.e: git config branch.master.remote origin git config branch.master.merge refs/heads/master Which should give you the equivalent of a branch created with -t. On 04/02/13 20:12, Ian Lyna

Git confusion

Hi all, If I do git clone darcs.haskell.org:/srv/darcs/ghc.git cd ghc git show origin then the output is [...] Local branch configured for 'git pull': master merges with remote master [...] However, none of: git remote rm origin git remote add origin darcs.h

Re: [commit: ghc] master: add $(CrossCompilePrefix) to hp2ps (#7639) (b0fad0c)

On 04/02/13 11:52, Gabor Greif wrote: Hi Simon, all, here is me my new patch: $ git show 95303e2b96f0630a051544b216cf4530d37dbaba commit 95303e2b96f0630a051544b216cf4530d37dbaba Author: Gabor Greif Date: Fri Nov 23 17:54:00 2012 +0100 Allow different customizations per cross target

Re: [commit: ghc] master: add $(CrossCompilePrefix) to hp2ps (#7639) (b0fad0c)

Hi Simon, all, here is me my new patch: $ git show 95303e2b96f0630a051544b216cf4530d37dbaba commit 95303e2b96f0630a051544b216cf4530d37dbaba Author: Gabor Greif Date: Fri Nov 23 17:54:00 2012 +0100 Allow different customizations per cross target by obtaining CrossCompilePrefix from mk/

Re: Compiling DynFlags is jolly slow

On 31/01/13 18:57, Ian Lynagh wrote: On Thu, Jan 31, 2013 at 12:23:02PM -, GHC wrote: I can't compile `DynFlags` on my 256MB Raspberry Pi. Could we do something about having less auto-generated code in this module please? -- Ticket URL:

Re: [commit: ghc] master: Follow random submodule change (ca5d15a)

Ian, That still doesn't work: > Cloning into 'libraries/random'... > fatal: reference is not a tree: 2117e38729adaa4f465f3c5b7a8c5c4d77702d3f > Unable to checkout '2117e38729adaa4f465f3c5b7a8c5c4d77702d3f' in submodule > path 'libraries/random' Also: http://darcs.haskell.org/ghcBuilder/builders