| Re: [AD] Problems with gcc 3.1 |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Vincent Penquerc'h wrote:
>
>
> > > If you have gcc 3.1, can you test it please? I don't see
> > why `fsqrt'
> > > needs to be "built-in", whatever that means (ok, some optimisations
> > > could probably be had).
> >
> > It looks like gcc 3.1 really takes it as an internal thing:
>
> Try compiling with as ANSI compliant. I believe there can be no
> such builtins then. This also means that there must be a libcall
> to such a function. String stuff like strcpy are builtins as well
> when compiling with optimizations.
Sorry, but I don't see the point. You can't force users to compile with the
ANSI switch.
> Also, try taking the address of fsqrt, to see if it makes it treat
> it like a libcall.
> That *may* mean that a given combination of flags used in an
> Allegro program would make GCC see these symbols as non-builtins,
> but it might not be simple.
But: what about users? It isn't just the library.
IMHO this name is a problem, it collides with some libc and now with gcc.
SET
--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set@xxxxxxxxxx set@xxxxxxxxxx
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013