This is now Trac #11390.
On 27 mai, 15:41, Jean-Pierre Flori wrote:
> I must admit that I do not know what that method call exactly does,
> but calling it resolve the mentionned bug.
> Moreover it is called in different places all over the file in a
> similar manner so I have the feeling that it
I must admit that I do not know what that method call exactly does,
but calling it resolve the mentionned bug.
Moreover it is called in different places all over the file in a
similar manner so I have the feeling that it could be an acceptable
fix.
I'll open a trac ticket with that fix and a doctes
Adding
(self._parent).F.restore()
before calling
cdef GF2X_c r = GF2X_IrredPolyMod(GF2E_rep(self.x),GF2E_modulus())
fixes everything.
Not sure yet why it does not get called before in that situation...
On 27 mai, 15:03, Jean-Pierre Flori wrote:
> Putting sig_on/sig_off around:
>
Putting sig_on/sig_off around:
sig_on()
cdef GF2X_c r = GF2X_IrredPolyMod(GF2E_rep(self.x),
GF2E_modulus())
sig_off()
I get:
/home/jp/boulot/sage/sage-4.7.rc1/local/lib/python2.6/site-packages/
sage/rings/finite_rings/element_ntl_gf2e.so in
sage.rings.finite_rings.element_nt
Hi Jean-Pierre,
On 27 Mai, 14:31, Jean-Pierre Flori wrote:
> I'll take care of it with a fix hopefully.
It turns out that the error occurs in the list() method of a homset,
which starts with
sage: K = GF(1<<16,'a'); L = GF(1<<32,'b')
sage: self = K.Hom(L)
sage: D = self.domain()
sage: C = self.
I'll take care of it with a fix hopefully.
The value 16 is of course related to FF implementation.
>From 16 it uses NTL and GF2X.
There's something nasty occuring in charpoly() or deeper.
On 27 mai, 14:27, Simon King wrote:
> Hi Jean-Pierre,
>
> On 27 Mai, 14:08, Jean-Pierre Flori wrote:
>
> > I
Hi Jean-Pierre,
On 27 Mai, 14:08, Jean-Pierre Flori wrote:
> I'm using sage 4.7.rc1 on debian amd64, gcc 4.6.
> Can anybody reproduce that behavior, so we should open a trac ticket ?
> I could not find anything similar here or on trac.
> I'll continue investigating it anyway.
I confirm the erro
