Hello,
I have done a cython interface for the giac library. There is a version for
python and another one for sage.
I have opened the following trac:http://trac.sagemath.org/ticket/15226
Details and examples are available on my page :
http://www.math.jussieu.fr/~han/xcas/giacpy
Best regards,
On Tue, Sep 24, 2013 at 10:34:11AM -0700, Bill Janssen wrote:
> Hmmm, but that would replicate the fairly complicated Python code that it
> already uses to determine the proper flags.
>
> For the moment, I've fixed it by doing an "unset LDFLAGS" in the
> spkg-install file, but I think it's still
On Tue, Sep 24, 2013 at 9:02 AM, Simon King wrote:
> Hi Peter,
>
> On 2013-09-24, Peter Bruin wrote:
>> We already have FieldElement, which is a Cython class consisting of
>> methods, including is_unit(). Ignoring my opinion about C.ElementMethods
>> for a moment, why not just move the existing
Hmmm, but that would replicate the fairly complicated Python code that it
already uses to determine the proper flags.
For the moment, I've fixed it by doing an "unset LDFLAGS" in the
spkg-install file, but I think it's still a Sage bug to export empty
LDFLAGS if the user hasn't set them that wa
Hi Peter,
On 2013-09-24, Peter Bruin wrote:
> We already have FieldElement, which is a Cython class consisting of
> methods, including is_unit(). Ignoring my opinion about C.ElementMethods
> for a moment, why not just move the existing methods in
> FieldsElementMethods to FieldElement and the
Hi Simon,
>From my perspective, the only potential issue is speed. Even a Python
> function returning the constant "True" is quite slow. But I think, if
> speed matters, it should be possible to have a separate Cython module
> providing a class, say,
> sage.categories.element_methods.FieldElem
I tried building in from source and this is the error I got. any help would be
greatly appreciated.
Thanks!
Shahab
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/data2/sage-5.11/local/lib/gcc
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:
.
