GitLab

This is the new way of handling switch-jumps. The node contains a table
which maps (ranges of) input values to proj numbers. Compared to a
Cond-node this results in a clean consecutive sequence of Proj numbers
(no searching for a free number for the default_pn anymore) and allows
factoring multiple cases jumping to the same block in a single Proj
(though we still need the optimisation in cfopt for that).

They are reserved in ANSI-C so instead of _XXX we use XXX_ now.

(they were introduced when moving value_classes out of the descriptor)

This also means that dependent modules like bedbgout should be
initialized by begnuas.

The main change here is splitting new_ir_mode into new_int_mode,
new_reference_mode and new_float_mode. You can now specify
mantissa+exponent size in new_float_mode. This also changes:

- x86 80bit-FP mode is NOT a ieee754 don't put "ieee754" into functions
  names that can also handle x86 80bit fps
- Move ieee_descriptor_t from tarval module into ir_mode struct
  (and rename to float_descriptor_t)
- Introduce mode_Q which represents binary128 from ieee754
- You can ask float modes for mantissa/exponent sizes now
- Fix endianess when emitting big float values in begnuas
- A bunch of long double fixes in ia32: the mode there has 10bytes
  (80bit) but the variables typically are 12 or 16 byte big
- This fixes some problems of sparc binary128 handling

There were no users and no tarval support anyway.

If vrp can prove that both operand of an Or/Eor/Add never a bit set in
common then we can match them as each of these opcodes.

They're adding more noise than they provide gain in readability. They
also make extra work to keep up to date.

Fixes opt/fehler204 again.

Extend opt_manage framework with MANY_RETURNS condition.

Since normalize_n_returns might introduce unreachable code,
the order should be handled in the framework instead of the
optimization.

Fix opt/gap test.

Newer yComp (>= 1.3.14) can handle backslashes in strings.

Fixes test opt/fehler204

Dump array initialisers, which contain only bytes in the printable range, as strings instead of separate byte initialisers.

Eg.
[0] = 0x62
[1] = 0x6C
[2] = 0x61
[3] = 0x00]
becomes
[0...3] = "bla<NUL>"

TODO: Fix yComp, so it does not choke on backslashes.

It is just an unnecessary node, which the middleend does not understand and therefore cannot optimize.

Most of the world can handle C99 now, and the important rest (=msvc) can
handle long long as an extension.

They have been unnecessary aliases for is_SymConst_addr_ent() and
get_SymConst_entity().