GitLab

The new design simply lets you specify hex or not in tarval_snprintf.
This is way simpler than the previous machinery and enough for all users in
libfirm.

- This avoids missing cases when new arithmetic modes are introduced.
- This also fixes a wrong case in mode_overflow_on_unary_Minus()

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.

It was a member of ir_prog before but not correctly handled.

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

This should fix all known bugs, make the code easier to read and more
robust.

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.

[r28272]

[r28062]

[r27860]

[r27604]

- rework ir_phase API
(sorry for mixing these 2 things into 1 commit)

[r27285]

[r27277]

[r27153]

[r27145]

- There's a new type_dbg_info* that allows you to attach debug names to types
- get_type_name and get_type_ident are now more. The new ir_print_type
  and the usual ir_printf("%+F", type) help in most usage cases.
  But you should be aware that names are not guaranteed to be unique anymore
  (or positively said: You don't have no trouble anymore building unique names
   in code that creates types)
- No need to specify mode for new pointer types anymore (you can still do it
  with set_type_mode)

[r26909]

Allow the modulo-shift setting for reference modes. This is a work-around that fixes find_unsigned_mode().

[r26882]

[r26093]

- typo fixed

[r25784]

[r25780]

[r25553]

[r24618]

[r22938]

[r22937]

[r22889]