Remove mpz_neg etc inlining, done.

Add SItype etc to use autoconf.
Add possible mpq checking for num or den 1.

1 files changed, 8 insertions, 7 deletions

diff --git a/doc/tasks.html b/doc/tasks.html
index ed04314af..e79de2ab2 100644
--- a/doc/tasks.html
+++ b/doc/tasks.html
@@ -15,7 +15,7 @@
 
 <!-- NB. timestamp updated automatically by emacs -->
 <comment>
-  This file current as of 30 Apr 2001.  An up-to-date version is available at
+  This file current as of 3 May 2001.  An up-to-date version is available at
   <a href="http://www.swox.com/gmp/tasks.html">http://www.swox.com/gmp/tasks.html</a>.
 </comment>
 
@@ -117,12 +117,6 @@
      using them as function pointers.  The GLIBC trick of first defining a
      prototype then a macro looks like it won't work with the GMP
      <code>__gmpz</code> renamings.
-<li> Consider inlining <code>mpz_neg</code> as <pre>
-        if (src != dst) mpz_set (dst, src);
-        dst-&gt;_mp_size = - dst-&gt;_mp_size; </pre>
-     so that an in-place <code>mpz_neg(z,z)</code> can be a simple negation of
-     the size field.  Likewise for <code>mpz_abs</code>, and <code>mpq</code>
-     and <code>mpf</code> too.
 <li> <code>mpz_powm</code> and <code>mpz_powm_ui</code> aren't very
      fast on one or two limb moduli, due to a lot of function call
      overheads.  These could perhaps be handled as special cases.
@@ -418,6 +412,10 @@
      <code>PROLOGUE</code> style.
 <li> Combine the pa64 and pa64w directories.
 <li> Rename `mips2' =&gt; `mips32' and `mips3' =&gt; `mips64'.
+<li> <code>SItype</code> etc typedefs in gmp-impl.h could use an autoconf test
+     to determine whether <code>__attribute__ (mode)</code> is available, and
+     also whether <code>long long</code> is available for <code>DItype</code>
+     on non-gcc compilers.
 </ul>
 
 
@@ -516,6 +514,9 @@ near future, but are at least worth thinking about.
      would only be to add -m68881 to gcc, there's no gmp asm code using float,
      so perhaps it's just as easily left to the user to set
      <code>CFLAGS</code>.
+<li> <code>mpq</code> functions could perhaps check for numerator or
+     denominator equal to 1, on the assumption that integers or
+     denominator-only values might be expected to occur reasonably often.
 </ul>