4.2.1.8 The -Ofast test

  Problem:  Combining code that is compiled with -Ofast with code that
             is not results in inconsistent behaviour
  Fix By:   Compiling everything with -Ofast
  Waive If: The application does not use maths functions

  Example:  FAIL: fast test because some parts of the program were compiled with -Ofast and some were not.

This test checks that if part of the application was compiled with the -Ofast option, then all of it was compiled with this option. If only some parts are compiled with -Ofast then the parts that are not may not behave correctly as they will be expecting to receive accurate results from mathematical functions. For more details on this problem see: https://bugzilla.redhat.com/show_bug.cgi?id=1248744

If necessary the test can be disabled via the --skip-fast option and re-enabled via the --test-fast option.