From f8a45fa1b1764b34d4263eacd93411e8ba0484a4 Mon Sep 17 00:00:00 2001 From: Janne Grunau Date: Mon, 14 Mar 2011 22:59:19 +0100 Subject: replace FFmpeg with Libav in doc/ unless it stands for ffmpeg the program or is historic --- doc/optimization.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/optimization.txt') 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 -- cgit v1.2.3