Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inefficient polynomial powering for positive characteristic #7253

Closed
robertwb opened this issue Oct 20, 2009 · 5 comments
Closed

inefficient polynomial powering for positive characteristic #7253

robertwb opened this issue Oct 20, 2009 · 5 comments

Comments

@robertwb
Copy link
Contributor

One can take advantage of the fact that (a+b)p = ap + bp to quickly expand fn = fqp * fr (as r<p, and f^p is sparse, the resulting product is easy to compute).

See http://groups.google.com/group/sage-support/browse_thread/thread/38c3d619a7684a90

Upstream: Fixed upstream, in a later stable release.

Component: algebra

Issue created by migration from https://trac.sagemath.org/ticket/7253

@robertwb

This comment has been minimized.

@kedlaya
Copy link
Contributor

kedlaya commented Apr 5, 2016

Upstream: Reported upstream. No feedback yet.

@kedlaya
Copy link
Contributor

kedlaya commented Apr 5, 2016

comment:2

This behavior still appears to be present in 2016. Since the underlying representation of multivariate polynomials over a finite field appears to be in Singular, I've raised the issue upstream:

http://www.singular.uni-kl.de/forum/viewtopic.php?f=10&t=2523

For univariate polynomials over a finite field, the underlying representation is in FLINT, and there this seems to be handled correctly (although I haven't looked at the source or asked a developer to confirm):

sage: F = GF(7)
sage: P.<x> = PolynomialRing(F)
sage: u = (x^3 + 1)^3
sage: time v = u^(7^7); # a large power!
CPU times: user 1.17 s, sys: 44 ms, total: 1.21 s
Wall time: 1.21 s
sage: time v = u^1000000; # even larger! 
CPU times: user 1.58 s, sys: 36 ms, total: 1.62 s
Wall time: 1.62 s

@kedlaya
Copy link
Contributor

kedlaya commented Sep 23, 2017

Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, in a later stable release.

@kedlaya
Copy link
Contributor

kedlaya commented Sep 23, 2017

comment:3

This has been resolved upstream (see previous Singular link), so I propose to close this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants