Not new things, but in touched lines...

In some cases, the replacement is clearly not what is intended,
in those (where setup was called explicitly), I mostly renamed
`setup` to `_setup`.
The `test_ccompile_opt` is a bit confusing, so left it right now
(this will probably fail)

Pytest silence these normally anyway (capturing it to print it only on failure),
but occasionally I run with `-s` and I don't think this output adds anything unless
using printing to debug a specific test.
If nobody else cares about it nvm, just close it :).  Otherwise this cleans up everything
in the fast tests, except the f2py compilation right now.

  The normal behavior is to erase any flag that starts with
  `-m[a-z0-9\-\.]` when flag `-march` or `-mcpu` specified. for example:

    cc_normalize_flags([
       '-msse', '-msse2', '-msse3', '-mssse3', '-march=core-avx2'
    ])

    should be normalized to: ['-march=core-avx2']

  but in the case of `s390x`, on GCC flag `-march=arch[0-9]` doesn't  implies flag
  `-mzvector` which is required to enable zvector api. for example:

    cc_normalize_flags([
       '-mzvector', '-march=arch11', '-march=arch12', '-march=arch13']
    )

  should be normalized to: ['-mzvector', '-march=arch13']

  instead of: ['-march=arch13']