Gcc 1.39 and X386 1.1b (and xfig 2.0 p10)

[Hongjiu Lu]

In article <1991Jun27.173040.3890 at mav.com> stu at mav.com writes:
>After bringing up Roell's X386 1.1b, using gcc 1.39 (standard distribution,
>not the stuff with direct support for COFF and gdb), I tried to get
>xfig up.  I grabbed the latest copy I could find, xfig 2.0 pl10 and
>it compiled first try without any problems.  However, upon running
>it, it would crash the server when I tried to draw any lines.
>
>After turnning debug on in the server, and compiling with '-g' I
>was able to trace it down to the function miWideSegment (ddx/mi/miwideline.c)
>where it was getting a floating point exception error.  I used sdb
>to find the values in the offending line of code, could not find what
>was causing the error.  I then recompiled miwideline.c with the stock
>C compiler (cc) and linked X386 using gcc, and my problem was solved.
>
>There is apparently a bug in how gcc is dealing with floating point.
>I had one earlier occasion using xeyes where it failed with a floating
>point exception when using gcc. 
>
>I'm running an ACER 1100/33, 80387, and ISC 2.2. I haven't had any other
>noticeable problems, but then I hadn't been using gcc for very long either.
>
>So has anyone else seen this problem?  Is it possible that I have
>something wrong with my configuration?  When I made gcc, everything
>worked fine, and it passed the various tests that it came with.
>
>Anyway, hope this helps if anyone else out there has a similar problem.
>
>	-- Stu --
>-----------------------------------------------------------------------
>Stu Donaldson                   "Can't you understand what I'm saying?" 
>stu at mav.com                     "What happened?  Did you Fail Telepathy?"
>

I had the same problem regarding the floating point operation with
gcc 1.39. I had to use cc instead of gcc for some floating point
programs. Could anyone give us a clue?

Thanks.

H.J. Lu