my latest mail, after I checked in the changes which I believe is
right, did not include a tar.gz file indeed. Will create one later.
E.
On Fri, Oct 4, 2013 at 7:50 PM, Andrew Fiori wrote:
> I never did figure out how to grab the latest snapshot off the gf2x dev
> site, I had been working with t
I never did figure out how to grab the latest snapshot off the gf2x dev
site, I had been working with the tarballs linked in this thread, of which
I never tested one that worked (though, I believe we determined which
changes would fix the problem).
Right now that machine is being tortured by runnin
It seems I only sent my reply to Emmanuel.
So briefly:
- Andrew: can you please confirm 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
You're right about rand(). printf() does not matter here, as using the
computed value via the return code of main() suffices to "use" the value as
far as optimization is concerned.
Checked in a new test.
E.
On Tue, Sep 24, 2013 at 10:55 AM, Andrew Fiori wrote:
> On closer inspection, the s
On closer inspection, the sse2 test code in:
http://www.loria.fr/~thome/vrac/gf2x-201309240733-4b5636d.tar.gz
the previously linked
http://www.loria.fr/~thome/vracgf2x-201309232352-49027b2.tar.gz
and the code above all compile (gcc -msse2 test.c), however when they are
run the output of:
.
