GitLab

Especially, do not confirm consistent out edges.
This fixes ack/t7.c on SPARC.

This commit does:
- Remove tarval_reachable+tarval_unreachable, dataflow analysis rather
  use top/bottom instead of other special values.
- Rename tarval_undefined to tarval_unknown as it corresponds to the
  Unknown node (=a value which we don't know)
- Remove predefined tarval_top/tarval_bottom from tv.h and place the
  defines into combo.c
- Change compute_XXX constant folding functions to return tarval_unknown
  instead of tarval_bad if folding failed
- compute_Unknown in combo results in tarval_bottom == tarval_unknown
  this eliminates strange special cases in the Cond/Switch rules and the
  now unnecessary cprop_X list.

Also clean up the macro.

This can be used to effectively test aliasing in libfirm.

Deduce the mode automatically from the given entity.

This removes the strange entity/type duality and we get rid of union symconst_symbol.

This avoids problems where fixing Sels creates new Projs which must not
be changed. The previously broke valid cases in opt/structcall3.c for sparc.

This reverts commit bf8ff592
and fixes opt/ifconv7.c.

The tarval module has a maximally supported precision. Assert that no
modes with higher precision are created, otherwise the tarval module
will silently drop the higher bits on calculation. TODO: Change tarval
module to dynamically use smaller/bigger representations depending on
the mode.

Removed mode_LLs, mode_LLu, mode_Q for now as they are bigger than the
limit.

Fixes valgrind error

We couldn't generate sensible code for them anyway.

When killing the CopyB we have to use the CopyBs memory input instead of
the Call memory input. To do this I had to rework/improve a previous hack/fix
for const calls with compound return.

Most firm analyses behaved incorrectlye when: A called SymConst did not
have a method entity, assumed the code reachable by get_entity_irg is
the code called. These assumptions are wrong when doing crazy casts in C
or when dealing with weak symbols. This is fixed by introducing some
convenience functions: get_Call_callee(), get_entity_linktime_irg()

This also fixes issues where the no_critical_edges flag was not cleared.

All users of NEW_ARR_A used it to construct a simple array, yet noone
cared about it actually being an array with a length field in front. For
this simple use case you should use ALLOCAN.

This fixes backend/lower_call4.c (issue #113).

Types need not be in their final form after the new_entity so there is no
need to have _d variants like we have with all the graph nodes. You can easily
use set_entity_dbg_info() after construction.

Directly reading tp->align breaks (at least) for array types.