diff options
| author | arpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2001-10-24 02:26:49 +0000 |
|---|---|---|
| committer | arpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2001-10-24 02:26:49 +0000 |
| commit | 56a3cd32f2b7b509df4567391d689284eb335706 (patch) | |
| tree | 768501eb146ed31af98650349abef80230cdf2a3 /DOCS | |
| parent | e5f9e5b0573a9b1175fae0656bddf4daa4d3744f (diff) | |
| download | mpv-56a3cd32f2b7b509df4567391d689284eb335706.tar.bz2 mpv-56a3cd32f2b7b509df4567391d689284eb335706.tar.xz | |
hmm. am I a doxwriter?
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@2441 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/gcc-2.96-3.0.html | 49 |
1 files changed, 49 insertions, 0 deletions
diff --git a/DOCS/gcc-2.96-3.0.html b/DOCS/gcc-2.96-3.0.html new file mode 100644 index 0000000000..150b0bf267 --- /dev/null +++ b/DOCS/gcc-2.96-3.0.html @@ -0,0 +1,49 @@ +<HTML> +<BODY BGCOLOR=WHITE> + +<P> +<B>Question:</B> What is the problem with GCC 2.96 ? And with 3.x ? +</P> + +<P> +<B>Answer:</B> +</P> + +<P> +And for the people, who periodically asks what are the exact problems with +gcc 2.96, my answer: <I>we don't know.</I> We just see various bugreports mostly +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 +has different default optimization flags and they conflicts with our inline +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. +</P> + +<P> +I think that the gcc 2.96 should be fixed to be option-compatible with other +releases, but redhat guys refused to do it. If someone interested - ask +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 +<I>workaround</I> gcc 2.96 bugs... +We simply has no interest and time to do it. +</P> + +<P> +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 +supports intel asm syntax, and it caused the pipe bug. But it was a bug, +because gcc silently, without any warning, ignored the whole asm block. +*They* have fixed that, now it prints warning and doesn't skip the block. +(at least he told me, i didn't checked) +</P> + +<P> +Other gcc 3.x problems comes from broken libstdc++ or glibc header (std_*.h) +installation. They are not our fault. MPlayer compiles and works well with +gcc 3.x versions. <B>Only 2.96 is broken</B>, but it depends on many environment +elements, including gcc 2.96 release number, enabled mplayer features, etc. +<I>If it works for you using gcc 2.96, it doesn't mean it will work for everyone.</I> +</P> + +</BODY> +</HTML> |