--- Comment #6 from pinskia at gcc dot gnu dot org 2006-04-22 20:39 ---
THis is not a libgfortran bug but rather a bug in the libm on your system. The
libgfortran version of csqrt was fixed and works. Glibc's version was also
fixed at the same time.
--
pinskia at gcc dot gnu dot or
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-04-03 06:51
---
Recently updated glibc on my i686-pc-linux-gnu box and csqrt is now working.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25370
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2005-12-15 09:25
---
Adding a printf into the libgfortran csqrt() code:
re = REALPART (z);
im = IMAGPART (z);
printf ("input: %lg %lg\n", re, im);
shows that it is used in both cases, but the input value is crap in the
dynamic
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2005-12-12 22:14
---
(In reply to comment #2)
> I don't see this problem on FreeBSD with either static of dynamic
> linking. Note, in both cases, I am picking up csqrt() from libgfortran.
> What platform are you using?
It's mentionn
--- Comment #2 from kargl at gcc dot gnu dot org 2005-12-12 20:06 ---
I don't see this problem on FreeBSD with either static of dynamic
linking. Note, in both cases, I am picking up csqrt() from libgfortran.
What platform are you using? Is this another glibc problem? Does
-fdump-tree-
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2005-12-12 15:43
---
More info: when linked dynamically, the csqrt() function called is the
libgfortran one ([1] csqrt(z = ), line 708 in
"c99_functions.c") which gives bad results.
When linked statically, I don't know what happens,
