On Dec 7, 5:51 am, Bill Hart <[EMAIL PROTECTED]> wrote:
> This bug is quite possibly not in FLINT, but in GMP or even gcc
> itself. I use "static inline" throughout FLINT (earlier revisions did
> not, but I fixed this before FLINT 1.0) because the rules for "static
> inline" are the same in the c99 standard and in the gnuC "standard".
>
> I did also notice some posts online about problems in gcc 4.3 itself
> with this. So I don't know if they've all been fixed yet in the
> prerelease you have.
>
> Also, if I understand correctly, gcc 4.2 is supposed to warn me of any
> potential problems I'll have with inlines in 4.3, and nothing shows
> up. However I don't know why it doesn't warn about problems in GMP
> itself.

When I compile FLINT 1.0 (as part of 2.9.alpha1) on my 32-bit Debian
x86, with:
gcc version 4.2.3 20071014 (prerelease) (Debian 4.2.2-3)
I do get warnings.  Here's a small, representative chunk of
install.log:
gcc -std=c99 -I/home/cwitty/sage-2.9.alpha1/local/include/  -fPIC -
funroll-loops   -O3 -c mpn_extras.c -o mpn_extras.o
In file included from mpn_extras.c:33:
/home/cwitty/sage-2.9.alpha1/local/include/gmp.h:1600: warning: C99
inline functions are not supported; using GNU89
/home/cwitty/sage-2.9.alpha1/local/include/gmp.h:1600: warning: to
disable this warning use -fgnu89-inline or the gnu_inline function
attribute
/home/cwitty/sage-2.9.alpha1/local/include/gmp.h:1626: warning: C99
inline functions are not supported; using GNU89
/home/cwitty/sage-2.9.alpha1/local/include/gmp.h:1637: warning: C99
inline functions are not supported; using GNU89

So that does point to the actual problem being with GMP.

Carl

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to