summaryrefslogtreecommitdiff
path: root/doc/optimization.txt
diff options
context:
space:
mode:
authorDiego Biurrun <diego@biurrun.de>2005-06-12 16:11:40 +0000
committerDiego Biurrun <diego@biurrun.de>2005-06-12 16:11:40 +0000
commit0a46c9330af170c8092484f69e7dc1ab8e32c3f0 (patch)
treea9bc7aef4d8d02b237ceca0f68b7db0227afe0bc /doc/optimization.txt
parentc5a44f571586b524c8a4f71aa896d25a682318e7 (diff)
Rephrase a paragraph for ease of understanding, suggested by Mans.
Originally committed as revision 4379 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc/optimization.txt')
-rw-r--r--doc/optimization.txt18
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/optimization.txt b/doc/optimization.txt
index ac24976930..011e9e4f0f 100644
--- a/doc/optimization.txt
+++ b/doc/optimization.txt
@@ -10,15 +10,15 @@ stuff in the i386 directory or find some other functions in the C source to
optimize, but there aren't many left.
Understanding these overoptimized functions:
-As many functions, like the C ones tend to be a bit unreadable currently
-because of optimizations it is difficult to understand them (and write
-architecture specific versions, or optimize the C functions further) it is
-recommended to look at older CVS versions of the interesting files (just use
-ViewCVS at http://www1.mplayerhq.hu/cgi-bin/cvsweb.cgi/ffmpeg/?cvsroot=FFMpeg).
-Alternatively, look into the other architecture-specific versions in the i386/,
-ppc/, alpha/ subdirectories. Even if you don't exactly understand the
-instructions, it could help understanding the functions and how they
-can be optimized.
+As many functions tend to be a bit difficult to understand because
+of optimizations, it can be hard to optimize them further, or write
+architecture-specific versions. It is recommened to look at older
+CVS versions of the interesting files (just use ViewCVS at
+http://www1.mplayerhq.hu/cgi-bin/cvsweb.cgi/ffmpeg/?cvsroot=FFMpeg).
+Alternatively, look into the other architecture-specific versions in
+the i386/, ppc/, alpha/ subdirectories. Even if you don't exactly
+comprehend the instructions, it could help understanding the functions
+and how they can be optimized.
NOTE: If you still don't understand some function, ask at our mailing list!!!
(http://www1.mplayerhq.hu/mailman/listinfo/ffmpeg-devel)