0.8.5 is fairly old... :). Do you know what the flag does? Like, would it cause
register-usage-reduction or something which could screw up, or is it just
something random that makes no apparent difference? I'm asking this so I know
whether to add a check for it or just remove it completely, even for the gcc3 build.

Thanks for testing btw.

I reported against 0.8.5 because it's the first version FTBFSing with this that
I noticed: <http://buildd.debian.org/build.php?arch=&pkg=gst-ffmpeg>.

The flag was meant temporarily to sort out optimizations and enhance gcc, and
has been deprecated since 3.3 at least.  It's removal is described at
<http://gcc.gnu.org/gcc-4.0/changes.html> as follows:
"The options -freduce-all-givs and -fmove-all-movables have been discontinued.
They were used to circumvent a shortcoming in the heuristics of the old loop
optimization code with respect to common Fortran constructs. The new (tree) loop
optimizer works differently and doesn't need those work-arounds."

I think it's not important for a 3.3 build, but might enhance the loop
optimizations slightly, if the other loop enhancement options are not present,
but I won't test.

Applied, thanks.