From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Sage test failures on amd64
Date: Tue, 20 Apr 2010 08:04:40 -0500 [thread overview]
Message-ID: <1271768687.25341.0@pavilion64> (raw)
In-Reply-To: <201004200822.31153.cschwan@students.uni-mainz.de> (from cschwan@students.uni-mainz.de on Tue Apr 20 01:22:30 2010)
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
On 04/20/10 01:22:30, Christopher Schwan wrote:
>
> You surely mean _with_ "-fno-strict-aliasing" ?
>
>>
>> Steve
>
> Christopher
>
Christopher,
To clarify, the test failures I listed were for the two computers when
"-fno-strict-aliasing" _was_ added to the CFLAGS in building pari. Of course,
I did this in the ebuild with append-flags. The failures for the second
computer with "Killed/crashed" at the end of the failed test like,
sage -t -force_lib "devel/sage/sage/graphs/cliquer.pyx" #Killed/crashed
passed on the same computer when pari was built in which
"-fno-strict-aliasing" was _not_ added to the CFLAGS. I will check again and
report if otherwise. With "-fno-strict-aliasing" added I get 21 failures on
the laptop and 32 failures on the desktop; with 7 of the failures on the
desktop of the type "Killed/crashed".
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-04-20 14: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
2010-04-20 13:04 ` Steven Trogdon [this message]
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=1271768687.25341.0@pavilion64 \
--to=strogdon@d.umn.edu \
--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