RepoMirrors/mpv
1
0
Fork 0
mirror of https://github.com/mpv-player/mpv synced 2024-12-24 15:52:25 +00:00
Code Issues Releases Wiki Activity

corrections by Diego Biurrun <diego@biurrun.de>

Browse Source 
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@5055 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
jaf 2002-03-12 12:36:00 +00:00
parent 5b6fefd246
commit df367a7e2c
1 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
DOCS/gcc-2.96-3.0.html
View File

@ -12,7 +12,7 @@
<FONT CLASS="text"> <FONT CLASS="text">
<P> <P>
<B>Question:</B> What is GCC 2.96 ? I can't find it at GNU site. <B>Question:</B> What is GCC 2.96 ? I can't find it at the GNU site.
</P> </P>
<P> <P>
@ -39,35 +39,35 @@
</I></P> </I></P>
<P> <P>
And for the people, who periodically asks what are the exact problems with And for the people who periodically ask what the exact problems with
gcc 2.96, my answer: <I>we don't know exactly.</I> gcc 2.96 are, my answer: <I>We don't know exactly.</I>
There were various problems and new problems / bugs come up periodically. There were various problems and new problems / bugs come up periodically.
It is <I>not a single bug/problem</I>. We just see various bugreports, mostly It is <I>not a single bug/problem</I>. We just see various bug reports, mostly
gcc internal bugs, compiler syntax errors in source or bad code compiled. They gcc internal bugs, compiler syntax errors in source or bad code compiled. They
all are solved using different version of gcc. I understand that gcc 2.96 are all solved by using a different version of gcc. I understand that gcc 2.96
has different default optimization flags and they conflicts with our inline has different default optimization flags and they conflict with our inline
asm code, but we can't fix them, and we really don't want to fix them as they asm code, but we can't fix them, and we really don't want to fix them as they
work with other compilers or gcc versions, and the fix may cause speed loss. work with other compilers or gcc versions, and the fix may cause speed loss.
</P> </P>
<P> <P>
I think that the gcc 2.96 should be fixed to be option-compatible with other I think that gcc 2.96 should be fixed to be option-compatible with other
releases, but redhat guys refused to do it. If someone interested - ask releases, but Red Hat guys refused to do it. If someone is interested - ask
Eugene K., avifile author, he has a long mailing with them, because they had Eugene K., avifile author, he has a long mailing with them, because they had
the same problems with avifile. Finally he changed avifile source to the same problems with avifile. Finally he changed avifile source to
<I>workaround</I> gcc 2.96 bugs... <I>work around</I> gcc 2.96 bugs...
We simply has no interest and time to do it. We simply have no interest and time to do it.
</P> </P>
<P> <P>
Ah, and about the pipe-in-comment bug: it wasn't really our bug. Ah, and about the pipe-in-comment bug: it wasn't really our bug.
I've talked one of gcc maintainers, and he told me that gcc 2.96 and 3.x I've talked to one of the gcc maintainers, and he told me that gcc 2.96 and 3.x
supports intel asm syntax, and it caused the pipe bug. But it <I>is</I> a bug, support Intel asm syntax, and it caused the pipe bug. But it <I>is</I> a bug,
because gcc <I>silently</I>, without any warning, ignored the whole asm block! because gcc <I>silently</I>, without any warning, ignored the whole asm block!
</P> </P>
<P> <P>
Other gcc 3.x problems comes from broken libstdc++ or glibc header (std_*.h) Other gcc 3.x problems come from a broken libstdc++ or glibc header (std_*.h)
installation. They are not our fault. MPlayer compiles and works well with installation. They are not our fault. MPlayer compiles and works well with
gcc 2.95.3 (<B>MEncoder</B> won't work with 2.95.2 because it miscompiles gcc 2.95.3 (<B>MEncoder</B> won't work with 2.95.2 because it miscompiles
some MMX instructions). <B>2.96 and 3.0.x are broken</B>, but it depends on some MMX instructions). <B>2.96 and 3.0.x are broken</B>, but it depends on
@ -91,9 +91,9 @@ Also read <A HREF="users_against_developers.html">this</A> text !!!</P>
<P> <P>
No. You are wrong! No. You are wrong!
Several projects (mostly which contain highly optimized inline asm code) Several projects (mostly those which contain highly optimized inline asm code)
had problems with gcc 2.96. For example: avifile, MESA / DRI, Wine, ffmpeg, had problems with gcc 2.96, for example: avifile, MESA / DRI, Wine, ffmpeg,
lame, NuppelVideo, MySQL. But other projects already workarounded gcc bugs lame, NuppelVideo, MySQL. But other projects already worked around gcc bugs
(changed code which triggered compiler bugs) so they work for now. (changed code which triggered compiler bugs) so they work for now.
</P> </P>
@ -112,11 +112,11 @@ It only means that you are lucky, until you find a problem. But don't forget the
<B>No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96</B> ! <B>No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96</B> !
<P> <P>
<B>Question:</B> Ok. Understood. But I want to give it a try... how to compile with gcc 2.96? <B>Question:</B> OK. Understood. But I want to give it a try... how to compile with gcc 2.96?
</P> </P>
<P> <P>
<B>Answer:</B> Really? Are you sure? Ok. You know... here it is: ./configure --disable-gcc-checking <B>Answer:</B> Really? Are you sure? OK. You know... here it is: ./configure --disable-gcc-checking
</P> </P>
<P> <P>