On 21/04/2011 12:29, Felipe Almeida Lessa wrote:
On Thu, Apr 21, 2011 at 8:08 AM, Simon Marlow wrote:
Right, it could be related to this. However this change was made to
eliminate some causes of NaNs, see:
http://hackage.haskell.org/trac/ghc/ticket/4914
So I'm very depressed if it managed to
On Thursday 21 April 2011 13:08:22, Simon Marlow wrote:
> On 20/04/2011 18:28, Ian Lynagh wrote:
> > On Wed, Apr 20, 2011 at 05:02:50PM +0200, Daniel Fischer wrote:
> >> So, is it possible that some change in ghc-7.0.3 vs. the previous
> >> versions
> >
> > Very little changed between 7.0.2 and 7.
On Thu, Apr 21, 2011 at 10:43 AM, Daniel Fischer
wrote:
> On Thursday 21 April 2011 17:18:47, Chris Kuklewicz wrote:
>> I tried "ghc --make -fforce-recomp simpleTest.hs" with -O0 and -O1 and
>> -O2 on OS X with 64-bit ghc-7.0.3
>>
>> All versions ran without printing errors.
>
> I seem to recall t
On Thursday 21 April 2011 17:18:47, Chris Kuklewicz wrote:
> I tried "ghc --make -fforce-recomp simpleTest.hs" with -O0 and -O1 and
> -O2 on OS X with 64-bit ghc-7.0.3
>
> All versions ran without printing errors.
I seem to recall that GHC produces sse2 code on x86_64. If that's correct,
the eff
I tried "ghc --make -fforce-recomp simpleTest.hs" with -O0 and -O1 and -O2 on OS
X with 64-bit ghc-7.0.3
All versions ran without printing errors.
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/li
On Thu, Apr 21, 2011 at 8:08 AM, Simon Marlow wrote:
> Right, it could be related to this. However this change was made to
> eliminate some causes of NaNs, see:
>
> http://hackage.haskell.org/trac/ghc/ticket/4914
>
> So I'm very depressed if it managed to introduce NaNs somehow.
>
> Could someone
On 20/04/2011 18:28, Ian Lynagh wrote:
On Wed, Apr 20, 2011 at 05:02:50PM +0200, Daniel Fischer wrote:
So, is it possible that some change in ghc-7.0.3 vs. the previous versions
Very little changed between 7.0.2 and 7.0.3. The only thing that jumps
out to me as possibly being relevant is:
di
On Wednesday 20 April 2011 21:55:51, Dan Doel wrote:
>
> It's not a statistics bug. I'm reproducing it here using just
> vector-algorithms.
Yep. Attached a simple testcasewhich reproduces it and uses only vector and
vector-algorithms.
>
> Fill a vector of size N with [N..1], and (intro) sort i
On Wed, Apr 20, 2011 at 3:01 PM, Daniel Fischer
wrote:
> I'm sure it's not criterion, because after I've found that NaNs were
> introduced to the resamples vectors during sorting (check the entire
> vectors for NaNs before and aftersorting, tracing the count; before: 0,
> afterwards often quite a
On Wednesday 20 April 2011 20:25:34, Bryan O'Sullivan wrote:
> On Wed, Apr 20, 2011 at 10:44 AM, Daniel Fischer <
>
> daniel.is.fisc...@googlemail.com> wrote:
> > I'll prepare a bundle, I'm afraid it won't be small, though. And it
> > might be architecture dependent, so I can't guarantee that you
On Wed, Apr 20, 2011 at 10:44 AM, Daniel Fischer <
daniel.is.fisc...@googlemail.com> wrote:
> I'll prepare a bundle, I'm afraid it won't be small, though. And it might
> be architecture dependent, so I can't guarantee that you will be able to
> reproduce it. But Bryan said on IRC yesterday that ot
On Wednesday 20 April 2011 19:11:07, Roman Leshchinskiy wrote:
> Daniel Fischer wrote:
> > Further investigation of the sorting code in vector-algorithms
> > revealed no bugs there, and if the runtime was forced to keep a keen
> > eye on the indices, by replacing unsafeRead/Write/Swap with their
>
On Wed, Apr 20, 2011 at 05:02:50PM +0200, Daniel Fischer wrote:
>
> So, is it possible that some change in ghc-7.0.3 vs. the previous versions
Very little changed between 7.0.2 and 7.0.3. The only thing that jumps
out to me as possibly being relevant is:
diff -ur 7.0.2/ghc-7.0.2/compiler/native
Daniel Fischer wrote:
>
> Further investigation of the sorting code in vector-algorithms revealed
> no bugs there, and if the runtime was forced to keep a keen eye on the
> indices, by replacing unsafeRead/Write/Swap with their bounds-checked
> counterparts or by 'trace'ing enough of their uses, th
Investigating the appearance of NaN in criterion's output, I found that
NaNs were frequently introduced into the resample vectors when the
resamples were sorted.
Further investigation of the sorting code in vector-algorithms revealed no
bugs there, and if the runtime was forced to keep a keen e
15 matches
Mail list logo