Due to the bug, the opcode name of phi nodes are never printed in the
first dump of the backend (...-begin.vcg).

Andreas Fried authored Aug 02, 2013 and yb9976 committed Sep 04, 2013

This covers two cases (assuming no aliasing operations in between the nodes):

Firstly, a Store node whose destination lies completely within the CopyB's
destination can be deleted.

Secondly, if a previous CopyB (A) writes to the source of CopyB to be optimized
(B), we can use A's source pointer for further optimizations. If A's source is
constant, we can change B to read from A's source.  Cases with offsets are not
handled.

Andreas Fried authored Aug 02, 2013 and yb9976 committed Sep 04, 2013

When following the Memory chain for a Store, a CopyB node may be skipped, if
both its destination and source do not alias with the Store's destination.

This is a major Makefile refactoring:
differentiate between:
- source files in $(srcdir)
- generated files in $(top_builddir)/gen
- object files in $(top_builddir)/$(variant)/ aka $(builddir)
- documentation in $(top_builddir)/doc

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.

Entities need not be in their final form after the new_entity call, 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.

It is not usefull for optimization in most languages:
- In C/C++ you can't really change the value of enum constants as casting
  from/to integer has to produce the expected results.
- In Java (and other OO languages) enum members are objects so the
  libfirm enumeration type can't be used there anyway

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.

- fix: not just aggregate parameters need special handling but also
  aggregate return types.
- don't just look at the called function but also on the call type.

This is a type which is aggregated from multiple primtive/simple
elements. In libfirm such a type cannot be represented as a mode.

few typo fix

This allows users - such as Special Instruction creation for
reconfigurable microarchitectures - to override the backend's
predicate.

This removes all predecessors from Syncs which are reachable through a path
beginning at another predecessor.