Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add a workaround to recognise I/_Complex_I as complex arguments. Although | stefanf | 2004-09-03 | 1 | -1/+2 |
| | | | | | the GCC manual claims that the expression 1.0fi has type float _Complex, __builtin_types_compatible_p(float _Complex, __typeof__(1.0fi))) yields 0. | ||||
* | Use the keyword '_Complex' rather than the macro 'complex' since | stefanf | 2004-09-03 | 1 | -4/+4 |
| | | | | applications are allowed to undefine the latter. | ||||
* | Embarrassing typo: s/nextbyint/nearbyint/ | stefanf | 2004-09-03 | 1 | -1/+1 |
| | |||||
* | Implement C99's standard header <tgmath.h>. It provides type-generic macros | stefanf | 2004-08-08 | 1 | -0/+166 |
for the <math.h> and <complex.h> functions that have float, double and long double implementations. Such type-generic macros expand to an actual function, depending on the types of the macro arguments, eg. if <tgmath.h> is included, the invocation cos(1.0f) calls the function cosf(). |