We only use control flow scc analysis.

== and != comparisons are always lowered with the "or trick" so no need
to have the other lowering code around.

This avoids constant testing whether an output buffer was specified or
the global accumulation buffer should be used. Also remove pointless
return values.

Projs are not scheduled anymore for a long time.

These are remnants from back when the prologue was added early and scheduling was not done, yet.
They were there to help the scheduler not to move an IncSP before the copy from sp to bp and thus having two values in sp live at the same time.

Directly use in_reqs => [ ... ], out_reqs => [ ... ].

They only produce a single result and having mode_T is unnecessary.
This could be improved, i.e. use both results.
But I just corrected the current usage.

- Add several new tests
- Move some tests from tarval_floatops to the improved "framework" in
  tarval_calc

Do this by combining it with the existing to_ascii/from_ascii tests.

- remove get_mode_nan() as there is not just a single NaN values but several
  different ones.
- introduce new_tarval_nan() which allows to construct signaling and
  quiet NaNs with payload.
- introduce tarval_is_snan() and tarval_is_qnan() to help unittests.