|
2440
|
1 <HTML>
|
|
|
2 <BODY BGCOLOR=WHITE>
|
|
|
3
|
|
|
4 <P>
|
|
|
5 <B>Question:</B> What is the problem with GCC 2.96 ? And with 3.x ?
|
|
|
6 </P>
|
|
|
7
|
|
|
8 <P>
|
|
|
9 <B>Answer:</B>
|
|
|
10 </P>
|
|
|
11
|
|
|
12 <P>
|
|
|
13 And for the people, who periodically asks what are the exact problems with
|
|
|
14 gcc 2.96, my answer: <I>we don't know.</I> We just see various bugreports mostly
|
|
|
15 gcc internal bugs, compiler syntax errors in source or bad code compiled. They
|
|
|
16 all are solved using different version of gcc. I understand that gcc 2.96
|
|
|
17 has different default optimization flags and they conflicts with our inline
|
|
|
18 asm code, but we can't fix them, and we really don't want to fix them as they
|
|
|
19 work with other compilers or gcc versions, and the fix may cause speed loss.
|
|
|
20 </P>
|
|
|
21
|
|
|
22 <P>
|
|
|
23 I think that the gcc 2.96 should be fixed to be option-compatible with other
|
|
|
24 releases, but redhat guys refused to do it. If someone interested - ask
|
|
|
25 Eugene K., avifile author, he has a long mailing with them, because they had
|
|
|
26 the same problems with avifile. Finally he changed avifile source to
|
|
|
27 <I>workaround</I> gcc 2.96 bugs...
|
|
|
28 We simply has no interest and time to do it.
|
|
|
29 </P>
|
|
|
30
|
|
|
31 <P>
|
|
|
32 Ah, and about the pipe-in-comment bug: it wasn't really our bug.
|
|
|
33 I've talked one of gcc maintainers, and he told me that gcc 2.96 and 3.x
|
|
|
34 supports intel asm syntax, and it caused the pipe bug. But it was a bug,
|
|
|
35 because gcc silently, without any warning, ignored the whole asm block.
|
|
|
36 *They* have fixed that, now it prints warning and doesn't skip the block.
|
|
|
37 (at least he told me, i didn't checked)
|
|
|
38 </P>
|
|
|
39
|
|
|
40 <P>
|
|
|
41 Other gcc 3.x problems comes from broken libstdc++ or glibc header (std_*.h)
|
|
|
42 installation. They are not our fault. MPlayer compiles and works well with
|
|
|
43 gcc 3.x versions. <B>Only 2.96 is broken</B>, but it depends on many environment
|
|
|
44 elements, including gcc 2.96 release number, enabled mplayer features, etc.
|
|
|
45 <I>If it works for you using gcc 2.96, it doesn't mean it will work for everyone.</I>
|
|
|
46 </P>
|
|
|
47
|
|
|
48 </BODY>
|
|
|
49 </HTML>
|
