summaryrefslogtreecommitdiffstats
path: root/DOCS/gcc-2.96-3.0.html
diff options
context:
space:
mode:
Diffstat (limited to 'DOCS/gcc-2.96-3.0.html')
-rw-r--r--DOCS/gcc-2.96-3.0.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/DOCS/gcc-2.96-3.0.html b/DOCS/gcc-2.96-3.0.html
index 8ba75d0f72..c129188f80 100644
--- a/DOCS/gcc-2.96-3.0.html
+++ b/DOCS/gcc-2.96-3.0.html
@@ -67,7 +67,7 @@ elements, including gcc 2.96 release number, enabled mplayer features, etc.
<P>
No. You are wrong!
Several projects (mainly which source contains high optimized inline asm code)
-had problems with gcc 2.96. For example: avifile, MESA / DRI, ffmpeg.
+had problems with gcc 2.96. For example: avifile, MESA / DRI, Wine, ffmpeg.
But other projects already workarounded gcc bugs (changed code which
triggered compiler bugs) so they work for now.
</P>