As they were just a single flag the name should reflect that. I did not
change arch_irn_flags_none, as that is not about a single flag.

The new code has less options and variants, if you call irg_verify()
verification is performed, regardless of DEBUG_libfirm, or NDEBUG being
set and regardless of firm verification setting switches. On the other
side no atomic dump and abort is performed anymore, the call has to do
this, though an irg_assert_verify() function has been added as a
convenience measure.
There has also been a complete rewrite of the actual checking performed.
The new code is simpler, should produce more consistent output and
can report more than one error.

the templates are now friendlier for usage outside of libfirm

They weren't used in a sensible way and their semantic for
non-arithmetic ops was unclear.
Also implicitely fixes a bunch of bugs where these where set but no op_index
was set at the same time.

Get away from the strange set_default_XXX_op style and instead let the
code modules register their node ops directly.

The opcode list was a member of irprog before which wasn't really
handled consistently. Also make sure opcodes are properly freed at
ir_finish().

memops are nodes that have memory inputs, you can generically query them
for their memory input. We can also get rid of get_fragile_op_mem in
favor of get_memop_mem.

Some backends create nodes in their lower_for_target phases already.
These nodes are placeholders for real backend nodes later, in contrast
they do not have register requirements or backend attributes. Simplified
this by allowing custom dumpers for them and leaving out the backend
node structs.

- The pns of X_regular and X_except are annotated in the opcode now.
- The memory input is annotated in the opcode now
- only nodes with X_regular, X_except are marked fragile

add unknown_jump opflag for the special case of a jump where we can't directly influence the destination and can't predict/change them

[r28143]

[r28127]