[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Another 1.4.x-specific Ruby failure

From: Peter Samuelson <peter_at_p12n.org>
Date: 2006-08-18 06:53:45 CEST

[Max Bowsher]
> My SWIG_RB_COMPILE is picking up -fno-strict-aliasing anyway (from
> Ruby, I assume).
> I'm getting reproducable failures with 1.4.x, yet trunk is fine.
> I'm working on amd64 Debian etch.

Probably still a ruby bug rather than a svn bug. We have had multiple
failures that look like this - the most recent was solved by building
all of ruby with -fno-strict-aliasing, but an earlier incarnation,
which happened on powerpc, was solved by building ruby with a different
version of gcc (4.0.2 vs. 4.0.3, if I remember correctly). I guess
that there's some dodgy code in ruby somewhere, which sometimes gets
compiled correctly and sometimes not, depending on whims of the gcc
optimiser on a given version and platform - that -fno-strict-aliasing
fixed it for us in one instance may have been an accidental side effect
of perturbing the optimiser just enough.

Received on Fri Aug 18 06:54:15 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.