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.

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

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

also move copy_const_value from typerep/entity to irgmod.

We do not model them as a type anymore, but simply annotate
compound_member entities with a bit offset and bit size.

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.

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

Accordingly remove repr_class from entities.

- do not record properties on irgs anymore, always do it on the irgs
  entity; entity properties have to be a superset of the entities method
  type properties.
- Remove special irg_inline_property and use mtp_additional_properties
  instead

Remove now redundant (and sometimes wrong) location info from the panic messages.

This is used to implement C99 "inline"/GNU89 "extern inline" ie. an
entity which is externally defined but where we know an inlineable
definition anyway.

This commit removes the strange differentiation between
ir_visibility_external and ir_visibility_default. We now only have
ir_visibility_external for all symbols visible across compilation units.
You may or may not attach graphs/initializers to them.

unknown_type, code_type, none_type, unknown_entity reference are hold in
the irprog now. This makes handling more consistent since now all types
and entities are equally part of irprog.

public functions are already documented in their headers, no need to
repeat the comment at the definition site.

We already saved different entity attributes depending on the entity
type and an is_parameter flag. This unifies handling of different entity
types and introduces normal, method, parameter, label and
compound_member entities.

Use a special kind of entity on the frame type instead of a value_type
struct inside a method type. This makes replacement of function types
slightly easier (it's still a complex operation though) and handling in
the backend a bit more consistent since it's more or less a normal stack
access (with special offsets).

[r28340]

[r28141]

[r28127]

[r28062]

[r28043]