This is the new way of handling switch-jumps. The node contains a table
which maps (ranges of) input values to proj numbers. Compared to a
Cond-node this results in a clean consecutive sequence of Proj numbers
(no searching for a free number for the default_pn anymore) and allows
factoring multiple cases jumping to the same block in a single Proj
(though we still need the optimisation in cfopt for that).

They are reserved in ANSI-C so instead of _XXX we use XXX_ now.

They're adding more noise than they provide gain in readability. They
also make extra work to keep up to date.

They have been unnecessary aliases for is_SymConst_addr_ent() and
get_SymConst_entity().

API change: removes set_irg_outs_inconsistent and get_irg_outs_state
Use set_irg_state and is_irg_state instead!

This was done by removing unnecessary options/options that only
allowed marginal tweakings to improve performance while at the same time
making the interface cumbersome.

- 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

when calling exchange, set_irn_n, or set_irn_in.

fixes backend/inconsistent_outs test case

See http://www.libfirm.org/Unreachable_Code for details

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

[r28346]

[r28345]

[r28340]

[r28310]

remove get_irn_modename, get_irn_modeident from public API. It's unclear why we need an explicit combination of get_irn_mode and get_mode_name

[r28240]

[r28234]

[r28127]

[r28079]

[r28043]

[r28021]

[r28020]

differentiate between Bad and Deleted (because of exchange) nodes, this avoid some invalid memory accesses when trying to get irg from a Bad node

[r28019]

[r27944]

[r27833]

[r27762]

[r27346]

[r27328]