RE: [AD] Problems with gcc 3.1

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


Title: RE: [AD] Problems with gcc 3.1

> > 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.

I was thinking that if ANSI compliance makes it have fsqrt as a
function, then there probably is a way to tell the compiler to
do it specifically (and this option would then be turned on by
the ANSI compliance switch), so Allegro could use this switch.

--
Vincent Penquerc'h



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/