1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
|
# ====================================================================
#
# compat.cdl
#
# Maths library compatibility related configuration data
#
# ====================================================================
## ####ECOSGPLCOPYRIGHTBEGIN####
## -------------------------------------------
## This file is part of eCos, the Embedded Configurable Operating System.
## Copyright (C) 1998, 1999, 2000, 2001, 2002, 2013 Free Software Foundation, Inc.
##
## eCos is free software; you can redistribute it and/or modify it under
## the terms of the GNU General Public License as published by the Free
## Software Foundation; either version 2 or (at your option) any later
## version.
##
## eCos is distributed in the hope that it will be useful, but WITHOUT
## ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
## FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
## for more details.
##
## You should have received a copy of the GNU General Public License
## along with eCos; if not, write to the Free Software Foundation, Inc.,
## 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
##
## As a special exception, if other files instantiate templates or use
## macros or inline functions from this file, or you compile this file
## and link it with other works to produce a work based on this file,
## this file does not by itself cause the resulting work to be covered by
## the GNU General Public License. However the source code for this file
## must still be made available in accordance with section (3) of the GNU
## General Public License v2.
##
## This exception does not invalidate any other reasons why a work based
## on this file might be covered by the GNU General Public License.
## -------------------------------------------
## ####ECOSGPLCOPYRIGHTEND####
# ====================================================================
######DESCRIPTIONBEGIN####
#
# Author(s): jskov
# Original data: jlarmour
# Contributors: ilijak
# Date: 1999-07-07
#
#####DESCRIPTIONEND####
#
# ====================================================================
cdl_interface CYGINT_LIBM_COMPAT {
requires 1 == CYGINT_LIBM_COMPAT
}
cdl_component CYGSEM_LIBM_COMPAT_IEEE_ONLY {
display "IEEE-only"
default_value 0
implements CYGINT_LIBM_COMPAT
description "
The math library can be hard-coded to only
behave in one compatibility mode - IEEE. This
cannot be changed at run-time. IEEE mode is the
most minimal of the compatibility modes, and so
this will best help code size and speed, as well
as omitting the code for other compatibility
modes. If not defined, the math library can be
set at run-time to any of the supported
compatibility modes."
cdl_option CYGSEM_LIBM_IEEE_API_INLINE {
display "Inline IEEE754 API wrappers"
default_value 0
description "
IEEE754 API functions are just wrappers for
core functions. This introduces indirection which can can be
avoided by inlining. This will also prevent GCC from rendering
these functions as builtin. The HAL can override for a set of functions
by providing a list of builtin functions."
}
}
cdl_component CYGNUM_LIBM_COMPATIBILITY {
display "Default mode"
flavor booldata
requires CYGPKG_LIBC
implements CYGINT_LIBM_COMPAT
legal_values { "POSIX" "IEEE" "XOPEN" "SVID" }
default_value { "POSIX" }
define CYGPKG_LIBM_COMPATIBILITY_DEFAULT
description "
If you want to have support for more than one
compatibility mode settable at run-time, rather
than hard-coded IEEE mode, this component lets
you choose which mode should be the default."
cdl_option CYGNUM_LIBM_COMPAT_DEFAULT {
display "Numeric representation"
flavor data
calculated { \
CYGNUM_LIBM_COMPATIBILITY == "POSIX" ? "CYGNUM_LIBM_COMPAT_POSIX" :\
CYGNUM_LIBM_COMPATIBILITY == "IEEE" ? "CYGNUM_LIBM_COMPAT_IEEE" :\
CYGNUM_LIBM_COMPATIBILITY == "XOPEN" ? "CYGNUM_LIBM_COMPAT_XOPEN" :\
CYGNUM_LIBM_COMPATIBILITY == "SVID" ? "CYGNUM_LIBM_COMPAT_SVID" :\
"<undefined>" \
}
description "
This option automatically defines the default compatibility
mode for numeric representation in terms of the values used
to set that mode at run-time."
}
cdl_option CYGOPT_LIBM_COMPAT_POSIX_IEEE {
display "POSIX return NaN for out-of-domain argument."
active_if { CYGNUM_LIBM_COMPATIBILITY == "POSIX" }
default_value 0
description "Later POSIX specification states that functions
may return either NaN (like IEEE), or implementation defined
value when argument is out of domain. For backward compatibility
default value is set to 0."
}
}
cdl_option CYGFUN_LIBM_SVID3_scalb {
display "SVID3-style scalb()"
default_value 1
description "
SVID3 defined the scalb() function as double
scalb(double, double) rather than double
scalb(double, int) which is used by IBM, DEC, and
probably others. Enabling this option chooses
the (double, double) version. Note there is a
function double scalbn(double, int) which is
unaffected by this choice."
}
cdl_option CYGSYM_LIBM_NO_XOPEN_SVID_NAMESPACE_POLLUTION {
display "Reduce namespace pollution"
default_value 0
description "
If you do not want to use either the X/Open or
SVID3 compatibility modes, you may want to define
this option to reduce the chance of namespace
pollution. This is particularly likely to occur
here as these standards define symbols with
names that often appear in applications, such as
exception, DOMAIN, OVERFLOW, etc. If your
application also used these names, it may cause
problems."
}
cdl_option CYGSEM_LIBM_USE_STDERR {
display "Output to stderr for math errors"
requires !CYGSEM_LIBM_COMPAT_IEEE_ONLY
requires CYGPKG_LIBC_STDIO
default_value 0
description "
The SVID3 standard says that error
messages should be output on the stderr console
output stream. This option allows this ability
to be explicitly controlled. However, this still
only has an effect in SVID3 compatibility mode."
}
|
