Mercurial > mplayer.hg
annotate DOCS/gcc-2.96-3.0.html @ 4982:6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
ocassional misc fixes
| author | gabucino |
|---|---|
| date | Thu, 07 Mar 2002 17:55:34 +0000 |
| parents | e67d400b6fde |
| children | b4c4d1abb7a4 |
| rev | line source |
|---|---|
| 2440 | 1 <HTML> |
|
4982
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
2 |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
3 <HEAD> |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
4 <STYLE> |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
5 .text |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
6 {font-family : Verdana, Arial, Helvetica, sans-serif; |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
7 font-size : 14px;} |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
8 </STYLE> |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
9 </HEAD> |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
10 |
| 2440 | 11 <BODY BGCOLOR=WHITE> |
|
4982
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4542
diff
changeset
|
12 <FONT CLASS="text"> |
| 2441 | 13 |
| 14 <P> | |
| 15 <B>Question:</B> What is GCC 2.96 ? I can't find it at GNU site. | |
| 16 </P> | |
| 17 | |
| 18 <P> | |
| 19 <B>Answer:</B> Read the <A HREF="http://gcc.gnu.org/gcc-2.96.html">official answer from GNU GCC team.</A> | |
| 20 </P> | |
| 2440 | 21 |
| 22 <P> | |
| 23 <B>Question:</B> What is the problem with GCC 2.96 ? And with 3.x ? | |
| 24 </P> | |
| 25 | |
| 26 <P> | |
| 27 <B>Answer:</B> | |
| 28 </P> | |
| 29 | |
|
4542
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
30 <P>Read in MySQL documentation :</P> |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
31 |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
32 <P><I> |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
33 Compiler Advisory: Several of our users have reported random crashes and |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
34 table corruption with MySQL binaries compiled with gcc two-dot-nine-six on |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
35 the x86 Linux platform. Although we were unable to duplicate the problems |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
36 ourselves or understand their exact cause, we suspect with a great degree of |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
37 confidence that the problem was compiler related. Replacing the faulty binary |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
38 with our binary always eliminated the problem. |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
39 </I></P> |
|
e67d400b6fde
mysql also goes haywire from sneaky-sucky-fucky gcc2.100-4
gabucino
parents:
3845
diff
changeset
|
40 |
| 2440 | 41 <P> |
| 42 And for the people, who periodically asks what are the exact problems with | |
| 2441 | 43 gcc 2.96, my answer: <I>we don't know exactly.</I> |
| 44 There were various problems and new problems / bugs come up periodically. | |
| 45 It is <I>not a single bug/problem</I>. We just see various bugreports, mostly | |
| 2440 | 46 gcc internal bugs, compiler syntax errors in source or bad code compiled. They |
| 47 all are solved using different version of gcc. I understand that gcc 2.96 | |
| 48 has different default optimization flags and they conflicts with our inline | |
| 49 asm code, but we can't fix them, and we really don't want to fix them as they | |
| 50 work with other compilers or gcc versions, and the fix may cause speed loss. | |
| 51 </P> | |
| 52 | |
| 53 <P> | |
| 54 I think that the gcc 2.96 should be fixed to be option-compatible with other | |
| 55 releases, but redhat guys refused to do it. If someone interested - ask | |
| 56 Eugene K., avifile author, he has a long mailing with them, because they had | |
| 57 the same problems with avifile. Finally he changed avifile source to | |
| 58 <I>workaround</I> gcc 2.96 bugs... | |
| 59 We simply has no interest and time to do it. | |
| 60 </P> | |
| 61 | |
| 62 <P> | |
| 63 Ah, and about the pipe-in-comment bug: it wasn't really our bug. | |
| 64 I've talked one of gcc maintainers, and he told me that gcc 2.96 and 3.x | |
| 2909 | 65 supports intel asm syntax, and it caused the pipe bug. But it <I>is</I> a bug, |
| 66 because gcc <I>silently</I>, without any warning, ignored the whole asm block! | |
| 2440 | 67 </P> |
| 68 | |
| 69 <P> | |
| 70 Other gcc 3.x problems comes from broken libstdc++ or glibc header (std_*.h) | |
| 71 installation. They are not our fault. MPlayer compiles and works well with | |
| 72 gcc 3.x versions. <B>Only 2.96 is broken</B>, but it depends on many environment | |
| 73 elements, including gcc 2.96 release number, enabled mplayer features, etc. | |
| 74 <I>If it works for you using gcc 2.96, it doesn't mean it will work for everyone.</I> | |
| 75 </P> | |
| 76 | |
| 3053 | 77 <P><B>Answer 2:</B></P> |
| 78 | |
| 79 <P> | |
| 80 Also read <A HREF="users_against_developers.html">this</A> text !!!</P> | |
| 81 | |
| 2441 | 82 <P> |
| 83 <B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>but</I> MPlayer | |
| 84 </P> | |
| 85 | |
| 86 <P> | |
| 87 <B>Answer:</B> | |
| 88 </P> | |
| 89 | |
| 90 <P> | |
| 91 No. You are wrong! | |
| 92 Several projects (mainly which source contains high optimized inline asm code) | |
| 3845 | 93 had problems with gcc 2.96. For example: avifile, MESA / DRI, Wine, ffmpeg, lame, NuppelVideo. |
| 2441 | 94 But other projects already workarounded gcc bugs (changed code which |
| 95 triggered compiler bugs) so they work for now. | |
| 96 </P> | |
| 97 | |
| 98 <P> | |
| 99 <B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>including</I> MPlayer | |
| 100 </P> | |
| 101 | |
| 102 <P> | |
| 103 <B>Answer:</B> | |
| 104 </P> | |
| 105 | |
| 106 Good. Be happy. But you must know, it depends on many environment | |
| 107 elements, including gcc 2.96 release number, enabled mplayer features, etc. | |
| 108 <I>If it works for you using gcc 2.96, it doesn't mean it will work for everyone!</I> | |
| 109 It only means that you are lucky, until you find a problem. But don't forget the | |
| 110 <B>No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96</B> | |
| 111 | |
| 112 <P> | |
| 113 <B>Question:</B> Ok. Understood. But I want to give it a try... how to compile with gcc 2.96? | |
| 114 </P> | |
| 115 | |
| 116 <P> | |
| 117 <B>Answer:</B> Really? Are you sure? Ok. You know... here is it: ./configure --disable-gcc-checking | |
| 118 </P> | |
| 119 | |
| 120 <P> | |
| 121 <B>Question:</B> No! I don't agree with you, because ... | |
| 122 </P> | |
| 123 | |
| 124 <P> | |
| 125 <B>Answer:</B> It doesn't matter. Keep your commets for yourself. We're not interested in gcc 2.96 stories. | |
| 126 </P> | |
| 127 | |
| 128 | |
| 129 </FONT> | |
| 2440 | 130 </BODY> |
| 131 </HTML> |