Hi,
Following this on upstream bug tracker.
E.
On Sunday, October 13, 2013 10:06:32 AM UTC+2, Dr David Kirkby wrote:
>
> drkirkby@hawk:~/unsets/sage-5.13.beta0$ ./sage -i gf2x-1.1.p0
> This looks like the first time you are running Sage.
> Updating various hardcoded paths...
> (Please wait at
irm that the latest tarball provided by
>> Emmanuel is fixed?
>> - if that's the case, I'll open a trac ticket to update the gf2x spkg
>> provided by Sage and it should make its way into Sage 5.12 or 5.13.
>>
>> Best,
>> JP
>>
>>
>> On Fr
could you pleae confirm that the fix I've committed to the gf2x main
branch fixes the issue you encounter ? This is a genuine bug which
deserves to be fixed, so:
- I care about whether my changes correct the issue.
- I don't mind creating a bugfix tarball if deemed useful.
On the other hand, if
2626, 0xabbabbab,
> 0xfeed1664);
> foo = _mm_mullo_epi16(foo, bar);
> if( _mm_extract_epi16(foo, 0) )
> {
>printf("XX");
>return 0;
> }
> else
> {
> printf("YY");
>return _mm_extract_epi16(foo
On Tuesday, September 24, 2013 2:41:58 AM UTC+2, Andrew Fiori wrote:
>
> The linked tar.gz file doesn't appear to fix the problem (I am assuming
> this is what you wanted me to test).
> It still tries to compile with sse2 on the non-sse 2 machine
>
> I am attaching the config.log as well as the o
On Friday, September 20, 2013 3:01:13 PM UTC+2, Andrew Fiori wrote:
>
> This is likely a build error bug on all systems which do not support SSE2
> but where building is done using the current version of gcc. It may also
> manifest as a runtime error on binary builds installed on systems which
Hmm, it turns out that it's not just any code that triggers this
behaviour. However, with the following test case I can reproduce the
problem quite deterministically:
(term1): strace -p `pidof sage.bin` -e trace='stat'
(term2):
sage: for i in range(100): float(1)/2
Regards,
E.
--~--~-
Hi,
I'm kind of puzzled with sage-3.1.4. When computing within the
interpreter, sage is frantically searching for some .pyx files,
unfortunately to no avail. This occurs even when no attached file is
new. At the end of this mail comes an excerpt of the strace output
(linux 64bit, compiled with g
