Nobody uses it currently, and it is a burden for everyone writing a new
pass.

! binds tighter than <

Most aspects of the fp_model flag would need to be enforced by
constructing the firm graph in a certain way. Setting it as a flag won't
help. Apart from that nearly nothing of the stuff was implemented
anyway.

They are considered low level operations now which just allocate/free a
block of memory on the stack. There is no highlevel typeinformation
attached anymore or support for heap allocation. Frontends/liboo should
provide their custom highlevel nodes if they need these features.

the templates are now friendlier for usage outside of libfirm

Templates are put in separate files now, making the main script more
generic in nature

It has been empty for nearly all systems. People who used to put stuff
in config.h can still create a config.h on their own and inject
-include (gcc) or /FI (msvc) into their CPPFLAGS.

We now recognize patterns like "array[variable + const]" as ir_no_alias,
if the array and variable are identical, but consts different.

The encoding field specifies the register number used when encoding an
instruction as machine code (and not as assembly)

ia32-fpunit     -> ia32-fpmath
ia32-opt        -> ia32-tune
ia32-soft-float -> new
Also fixes a too early invocation of set_arch_costs

Usually '-' was used as delimiter for hierarchically nested option
groups. We now try the completely remaining string as option if no
subgroup can be found, so options like "soft-float" work now (as long as
there is not subgroup named "soft")

This especially removes unused complicated error reporting mechanisms

In the previous buggy form it was creating an overly conservative
approximation.

(C1 - x) + C2 = (C1 + C2) - x
C1 - (x + C2) = (C1 - C2) - x
~(x + C) = (~C) - x (extended from ~(x + -1) = -x)
~(C - x) = x + (~C)
-(x + C) = (-C) - x