From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] Sage test failures on amd64
Date: Tue, 20 Apr 2010 08:22:30 +0200 [thread overview]
Message-ID: <201004200822.31153.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <1271726657.5976.0@ledaig>
On Tuesday 20 April 2010 03:24:11 Steven Trogdon wrote:
> On 04/19/10 - 12:29:01, Christopher Schwan wrote:
> > Hi,
> >
> > as some of us know there a lot of failures on amd64 when running
> > Sage's set of
> > tests. Now I found out that pari caused some of these (I dont know
> > exactly how
> > many, but I will do a full test run later), because it was compiled
> > without "-
> > fno-strict-aliasing". I have written a bug report for that:
> >
> > - https://bugs.gentoo.org/show_bug.cgi?id=316139
> >
> > In short: Add -fno-strict-aliasing to your CFLAGS and recompile pari
> > and there
> > should be less failing tests.
> >
> > Cheers,
> >
> > Christopher
>
> Christopher,
>
> This is significant! I'm listing test results here for comparison (pari
> w/ USE=gmp):
>
> Failures with CFLAGS="-march=k8 -O2 -pipe" and CXXFLAGS="${CFLAGS}" on
> a single processor laptop:
>
> sage -t -force_lib
> "devel/sage/doc/en/constructions/plotting.rst"
> sage -t -force_lib "devel/sage/sage/combinat/iet/strata.py"
> sage -t -force_lib "devel/sage/sage/interfaces/gp.py"
> sage -t -force_lib "devel/sage/sage/libs/pari/gen.pyx"
> sage -t -force_lib "devel/sage/sage/symbolic/expression.pyx"
> sage -t -force_lib
> "devel/sage/sage/gsl/probability_distribution.pyx"
> sage -t -force_lib "devel/sage/sage/lfunctions/lcalc.py"
> sage -t -force_lib "devel/sage/sage/plot/plot.py"
> sage -t -force_lib "devel/sage/sage/graphs/digraph.py"
> sage -t -force_lib "devel/sage/sage/graphs/graph.py"
> sage -t -force_lib "devel/sage/sage/misc/dist.py"
> sage -t -force_lib "devel/sage/sage/misc/cython.py"
> sage -t -force_lib "devel/sage/sage/misc/package.py"
> sage -t -force_lib
> "devel/sage/sage/functions/transcendental.py"
> sage -t -force_lib "devel/sage/sage/functions/special.py"
> sage -t -force_lib
> "devel/sage/sage/modules/vector_real_double_dense.pyx"
> sage -t -force_lib
> "devel/sage/sage/modules/vector_double_dense.pyx"
> sage -t -force_lib "devel/sage/sage/modular/modsym/space.py"
> sage -t -force_lib "devel/sage/sage/matrix/matrix1.pyx"
> sage -t -force_lib "devel/sage/sage/sets/set.py"
> sage -t -force_lib "devel/sage/sage/numerical/optimize.py"
>
> Failures with CFLAGS="-march=opteron -O2 -pipe" and
> CXXFLAGS="${CFLAGS}" on a dual processor, dual core desktop:
>
> sage -t -force_lib
> "devel/sage/doc/en/constructions/plotting.rst"
> sage -t -force_lib "devel/sage/sage/misc/cython.py"
> sage -t -force_lib "devel/sage/sage/misc/package.py"
> sage -t -force_lib "devel/sage/sage/misc/dist.py"
> sage -t -force_lib "devel/sage/sage/symbolic/expression.pyx"
> sage -t -force_lib "devel/sage/sage/lfunctions/sympow.py"
> sage -t -force_lib "devel/sage/sage/lfunctions/lcalc.py"
> sage -t -force_lib "devel/sage/sage/combinat/iet/strata.py"
> sage -t -force_lib
> "devel/sage/sage/combinat/words/suffix_trees.py" # Killed/crashed
> sage -t -force_lib
> "devel/sage/sage/combinat/posets/hasse_diagram.py" # Killed/crashed
> sage -t -force_lib "devel/sage/sage/interfaces/gp.py"
> sage -t -force_lib
> "devel/sage/sage/categories/coxeter_groups.py" # Killed/crashed
> sage -t -force_lib
> "devel/sage/sage/categories/finite_coxeter_groups.py" # Killed/crashed
> sage -t -force_lib "devel/sage/sage/matrix/matrix1.pyx"
> sage -t -force_lib "devel/sage/sage/plot/plot.py"
> sage -t -force_lib
> "devel/sage/sage/modular/hecke/submodule.py"
> sage -t -force_lib "devel/sage/sage/modular/abvar/abvar.py"
> sage -t -force_lib "devel/sage/sage/modular/modsym/space.py"
> sage -t -force_lib "devel/sage/sage/sets/set.py"
> sage -t -force_lib
> "devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py"
> sage -t -force_lib
> "devel/sage/sage/modules/vector_double_dense.pyx"
> sage -t -force_lib
> "devel/sage/sage/modules/vector_real_double_dense.pyx"
> sage -t -force_lib "devel/sage/sage/graphs/graph_list.py" #
> Killed/crashed
> sage -t -force_lib "devel/sage/sage/graphs/digraph.py"
> sage -t -force_lib "devel/sage/sage/graphs/cliquer.pyx" #
> Killed/crashed
> sage -t -force_lib "devel/sage/sage/graphs/graph.py"
> sage -t -force_lib
> "devel/sage/sage/gsl/probability_distribution.pyx"
> sage -t -force_lib "devel/sage/sage/numerical/optimize.py"
> sage -t -force_lib "devel/sage/sage/geometry/polyhedra.py" #
> Killed/crashed
> sage -t -force_lib "devel/sage/sage/libs/pari/gen.pyx"
> sage -t -force_lib
> "devel/sage/sage/functions/transcendental.py"
> sage -t -force_lib "devel/sage/sage/functions/special.py
>
> All of the tests with "Killed/crashed" passed on the desktop when pari
> was built without
> "-fno-strict-aliasing".
You surely mean _with_ "-fno-strict-aliasing" ?
>
> Steve
Christopher
next prev parent reply other threads:[~2010-04-20 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 17:29 [gentoo-science] Sage test failures on amd64 Christopher Schwan
2010-04-20 1:24 ` Steven Trogdon
2010-04-20 6:22 ` Christopher Schwan [this message]
2010-04-20 13:04 ` Steven Trogdon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004200822.31153.cschwan@students.uni-mainz.de \
--to=cschwan@students.uni-mainz.de \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox