This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
--- Sab 27/11/10, Corinna Vinschen ha scritto:
Data: Sabato 27 novembre 2010, 14:56 On Nov 26 14:18, Ralf Corsepius wrote:On 11/26/2010 11:19 AM, Corinna Vinschen wrote:catanf.c applyOn Nov 26 09:08, Ralf Corsepius wrote:Hi,
The functions in ctan.c, ctanf.c, catan.c and(i.e. they causehard-coded constants which are out of rangerun-time failures) oncompilation warnings and likely will causeincorrect on all targets.some (e.g. 16bit) targets and likely aresome targets.
Indeed, these values are potentially incorrect forhard-coded constants withHowever, they are used on BSD this way.
The patch below tries to replace thesedefines are available and[FLT|DBL_MAX] from<float.h>, when theseif these are nottries to fall back to the original constantsand [FLT|DBL]_MAX are POSIX andavailable.
Ralf
PS.: IMO, due to the fact<float.h>compiler, it's likely safethus should be available in any currentand to directly useto completely remove the hard-coded constants[FLT|DBL]_MAX.
Quite in contrast to the description of the real number functions. Just have a look into the "RETURN VALUE" section of the tan functions here: http://www.opengroup.org/onlinepubs/9699919799/functions/tan.html So why is that missing in the descriptions of the complex functions>
[...]Are there any mathematicians here who would like to provide their point of view to this problem?
Marco, since you added these functions, do you have a decided opinion?
at first glance ÂHUGE_VAL, ÂHUGE_VALF, should be better, bit I need to better check this problem.
Attachment:
newlib-complex.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |