Lines Matching full:should

6    Coding Standard and glibc specific conventions should be followed
9 2. ABI and symbols: the code should be written so it is suitable for inclusion
11 should be hidden and in the implementation reserved namespace according to
13 library archives should be usable to override libc symbols at link time (or
18 3. API: include headers should be suitable for benchmarking and testing code
19 and should not conflict with libc headers.
28 - Worst-case ULP error should be small in the entire input domain (for most
31 variant should not have > 5 ULP error if the goal is to be a drop in
32 replacement for a standard math function), this should be tested
34 The ulp tool is for this and runulp.sh should be updated for new functions.
44 this should be tested by direct tests (glibc test system may be used for it).
46 - Error handling code should be decoupled from the approximation code as much
52 result should be correct (within quality requirements, which are lower for
55 - Error bounds of the approximation should be clearly documented.
57 - The code should build and pass tests on arm, aarch64 and x86_64 GNU linux
61 The configurations that should be tested depend on the contribution.
64 - Common math code should be benchmarked on modern aarch64 microarchitectures
67 - Performance improvements should be documented (relative numbers can be
68 published; it is enough to use the mathbench microbenchmark tool which should
71 - Attention should be paid to the compilation flags: for aarch64 fma
72 contraction should be on and math errno turned off so some builtins can be
75 - The code should be reasonably performant on x86_64 too, e.g. some rounding
78 should be present: glibc and bionic use the same code on all targets. (This