This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: apparent bug
- To: baldamus at ira dot uka dot de
- Subject: Re: apparent bug
- From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Tue, 20 Jul 1999 08:15:56 +0200
- CC: gcc-bugs at gcc dot gnu dot org
- References: <Pine.SV4.3.96.990719184941.11994A-100000@i80s4>
> The problem was that the xdvi helper program failed to convert
> a certain font format, which is called the gf format, to another one,
> which is called the pk format. It seems to be a compiler problem
> since everything worked fine once I had rebuilt part of the teTeX
> package with the -O0 option. The default is to built with -O2.
> What I did was to rebuild everything in the directory
> teTeX-1.0/texk/kpathsea.
Thanks for your bug report. There is a known code generation bug in
the TeX area, in gcc 2.95. I'm not sure whether this is the particular
bug, or what the status of the bug is. Last I heard it was not going
to be fixed in gcc 2.95, because the bug report arrived too late for
anybody finding a proper fix in time.
OTOH, gcc 2.95 also significantly changed behaviour with respect to
programs violating the ISO C standard. If you want to experiment
further, please recompile xdvi with -fno-strict-aliasing -O2. This
option is necessary if the application is violating the ISO C aliasing
assumptions. AFAIK, at least libc might do such things in its inline
memcpy implementation (not sure about libc 5 here).
So, if you do try this, please let us know of the results.
Regards,
Martin