Re: good news and bad news on floating-point problems
The "unrecognizable insn" messages signal a compiler bug.
Are you using egcs? You could try to upgrade; if you are already at
1.0.3ish you should submit a bug report.
Transcendental functions like dlog are at the mercy of libm.so, however
good or bad it is. I'm not sure offhand whether libm is normally
compiled with traps. But if dlog causes SIGFPE it's not your code's fault.
Jeff
On Thu, 9 Jul 1998, Jesse Goldman wrote:
> g77 -c -O -fno-automatic -fno-second-underscore -fugly-complex -g
> -mieee-with-inexact -I/root/cernlib98/src/pawlib/paw
> -I/root/cernlib98/src/paw -I/root/cernlib98/src/paw/code
> -I/root/cernlib98/src/include -DCERNLIB_LINUX -DCERNLIB_UNIX
> -DCERNLIB_LNX -o archive/pafeyn.o pafeyn.F
> pafeyn.F: In subroutine `pafeyn':
> pafeyn.F:274: internal error--unrecognizable insn:
> (insn 1082 1081 1083 (set (reg:DF 452)
> (le:DF (float_extend:DF (reg:SF 448))
> (float_extend:DF (reg:SF 449)))) -1 (insn_list 1077 (insn_list
> 1081 (nil)))
> (expr_list:REG_DEAD (reg:SF 448)
> (nil)))
> ../../gcc/toplev.c:1138: Internal compiler error in function fatal_insn
--
To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: