aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar arpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2>2001-11-14 22:29:55 +0000
committerGravatar arpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2>2001-11-14 22:29:55 +0000
commit113336b4c373097e266c18526c8a1e2a95a5733f (patch)
tree7d4014ef61bbb26d0341cac7b7ef6c4e3911f14f
parentb8a80b1134a74014453f7ff988a04d51df3261c6 (diff)
updated. pipe bug not yet fixed
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@2910 b3059339-0415-0410-9bf9-f77b7e298cf2
-rw-r--r--DOCS/gcc-2.96-3.0.html6
1 files changed, 2 insertions, 4 deletions
diff --git a/DOCS/gcc-2.96-3.0.html b/DOCS/gcc-2.96-3.0.html
index c129188f80..f745f8b5de 100644
--- a/DOCS/gcc-2.96-3.0.html
+++ b/DOCS/gcc-2.96-3.0.html
@@ -42,10 +42,8 @@ We simply has no interest and time to do it.
<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.
-<I>They</I> have fixed that, now it prints warning and doesn't skip the block.
-(at least he told me, i didn't checked)
+supports 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!
</P>
<P>