summaryrefslogtreecommitdiff
path: root/doc/optimization.txt
diff options
context:
space:
mode:
authorJanne Grunau <janne-ffmpeg@jannau.net>2011-03-14 22:59:19 +0100
committerJanne Grunau <janne-libav@jannau.net>2011-03-16 22:01:01 +0100
commitf8a45fa1b1764b34d4263eacd93411e8ba0484a4 (patch)
treea5d27f5c5f38dd6fc28ce2f40b2748b09bd6a5dd /doc/optimization.txt
parenta03be6e1ba4cbf9984b0bbdb674704bbb2da6713 (diff)
replace FFmpeg with Libav in doc/
unless it stands for ffmpeg the program or is historic
Diffstat (limited to 'doc/optimization.txt')
-rw-r--r--doc/optimization.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/optimization.txt b/doc/optimization.txt
index 53cd21d22d..78e0077e30 100644
--- a/doc/optimization.txt
+++ b/doc/optimization.txt
@@ -17,7 +17,7 @@ Understanding these overoptimized functions:
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 recommended to look at older
-revisions of the interesting files (web frontends for the various FFmpeg
+revisions of the interesting files (web frontends for the various Libav
branches are listed at http://libav.org/download.html).
Alternatively, look into the other architecture-specific versions in
the x86/, ppc/, alpha/ subdirectories. Even if you don't exactly
@@ -201,7 +201,7 @@ Inline asm vs. external asm
---------------------------
Both inline asm (__asm__("..") in a .c file, handled by a compiler such as gcc)
and external asm (.s or .asm files, handled by an assembler such as yasm/nasm)
-are accepted in FFmpeg. Which one to use differs per specific case.
+are accepted in Libav. Which one to use differs per specific case.
- if your code is intended to be inlined in a C function, inline asm is always
better, because external asm cannot be inlined