GitLab

Avoid using the op_pin_state enum as that contains confusing additional
entries that are not valid on a node. The only remaining state for a
node is pinned/floating which we can simply represent with a 0/1 value.

There is no node left that uses it.

The previous approach put the irg link into the block attributes, so
while saving memory an extra indirection was necessary. Some testing
with valgrind massif+callgrind revealed that a direct link increses peak
memory usage by ~1% while also increasing runtime by ~1%. More
importantly the code gets a bit simpler and some strange corner cases can be
removed with the direct link.

- Compound type selection is performed with Member
- Array indexing is performed with Sel
- Instead of the simpleSel constructor functions you can use the normal Member
  constructors now
- The concept of array element entities has been removed, Sel nodes just
  contain a pointer to the array type now.

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

This node was used by OO code in the past, but newer versions of liboo
have their own node and don't need it anymore.

I don't really understand what it was supposed to do (because nodes
using/producing should be pretty much immovable anyway because of their
dependencies, so an additional pinning type appears unnecessary).
In practice there was no code differentiating between mem_pinned and exc_pinned.

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

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.

structs are bad in a library API. We provide setter functions for the
fields now.

You should specify the pinned attribute when calling new_ir_op and not
change it later.

Just state the copyright and the project the files belong to. You can
then find the COPYING file for the whole project.

This means floatingpoint calculation in a firm graph must be performed
in the mode specified (and may not be performed in a wider mode as
before).

so external users can set their own opcode functions.

You can still attach NoMem if no memory input is present.
This makes it more consistent with the Call node and fixes failing
get_ASM_mem in case of no memory input.