| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
FreeBSD test suite under lib/msun/tests
MFC after: 3 weeks
X-MFC with: r292328
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
|
|
| |
Also, don't compile the ldexpl(3) testcases on platforms that don't support
the libcall (technically only x86 right now). This makes this test buildable on
arm*/mips*/powerpc*
PR: 205449 [*]
MFC after: 1 week
Tested on: stable/10 (amd64/i386), head (amd64/i386)
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
| |
Use it consistently instead of i in the first loop
MFC after: 3 days
X-MFC with: 292492
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
| |
PR: 205448
MFC after: never
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
| |
It completely fails all assertions on i386 on both stable/9 and stable/10
PR: 205448
MFC after: 1 week
X-MFC to: stable/10
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
| |
- Use a separate variable for tracking the testcase count instead
of hardcoding the offset for the testcases
MFC after: 3 days
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also, don't compile the exp2l(3) testcases on platforms that don't support the
libcall (technically only x86 right now). This makes this test buildable on
arm*/mips*/powerpc*
Tested on: stable/10 (amd64/i386), head (amd64/i386)
PR: 205446 [*]
MFC after: 1 week
X-MFC to: stable/10
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
| |
Tested on: stable/10 (amd64/i386), head (amd64/i386)
PR: 205446
MFC after: 1 week
X-MFC to: stable/10
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
| |
Add test-invtrig to the list of tests
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
into the FreeBSD test suite
There's no functional change with these testcases; they're purposely
being left in TAP format for the time being
Other testcases which crash on amd64/i386 as-is have not been
integrated yet (they need to be retested on a later version of
CURRENT, as I haven't used i386 in some time)
MFC after: 3 weeks
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
| |
because `nums[]` is an array of long doubles
MFC after: 1 week
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Compare the fields that the AMD [1] and Intel [2] specs say will be
set once fnstenv returns.
Not all amd64 capable processors zero out the env.__x87.__other field
(example: AMD Opteron 6308). The AMD64/x64 specs aren't explicit on what the
env.__x87.__other field will contain after fnstenv is executed, so the values
in env.__x87.__other could be filled with arbitrary data depending on how the
CPU-specific implementation of fnstenv.
1. http://support.amd.com/TechDocs/26569_APM_v5.pdf
2. http://www.intel.com/Assets/en_US/PDF/manual/253666.pdf
Discussed with: kib, Anton Rang <anton.rang@isilon.com>
Reviewed by: Daniel O'Connor <darius@dons.net.au> (earlier patch; pre-generalization)
MFC after: 1 week
Sponsored by: EMC / Isilon Storage Division
Reported by: Bill Morchin <wmorchin@isilon.com>
|
|
|
|
|
|
|
|
| |
- Add missing <err.h> for err() and <sys/sysctl.h> for sysctlbyname()
- NULL -> 0 for 5th parameter of sysctlbyname()
Submitted by: Andriy Voskoboinyk <s3erios@gmail com>
Differential Revision: https://reviews.freebsd.org/D3442
|
|
|
|
|
|
|
|
| |
Reviewed by: jmmv, rpaulo
MFC after: 3 days
Phabric: D749
PR: 191676
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
| |
"initializer not constant" warning with gcc
Approved by: jmmv (mentor)
MFC after: 3 days
Phabric: D744
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
| |
This mutes warnings with clang
Approved by: rpaulo (mentor)
Reviewed by: das, kargl (both as part of a larger patch)
Phabric: D742
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
| |
and float precision properly.
|
|
|
|
|
|
| |
long double versions don't pass yet. (They are rather nit-picky cases,
so there's ongoing discussion with Bruce about whether it is worth the
performance cost.)
|
|
|
|
|
|
|
|
| |
because different tests have different ideas about what it means to be
"close enough" to the right answer, depending on the properties of the
function being tested. In the process, I fixed some warnings and
added a few more 'volatile' hacks, which are sufficient to make all
the tests pass at -O2 with clang.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
result depend on the cosine and sine of the imaginary part.
Small values are used in the new tests such that cosine and sine are well
defined.
Reviewed by: das
|
|
|
|
|
|
|
|
|
|
| |
are workarounds for various symptoms of the problem described in clang
bugs 3929, 8100, 8241, 10409, and 12958.
The regression tests did their job: they failed, someone brought it
up on the mailing lists, and then the issue got ignored for 6 months.
Oops. There may still be some regressions for functions we don't have
test coverage for yet.
|
|
|
|
|
| |
old and new, check the sign bits of both the remainder and the
quotient.
|
|
|
|
| |
wider than double. Thanks to Ian Lepore for catching the bug.
|
| |
|
| |
|
|
|
|
|
| |
long doubles. Thanks for clusteradm (simon) for making the needed
hardware available.
|
|
|
|
| |
I wrote these ages ago, but they've been failing until now.
|
| |
|
|
|
|
|
| |
these tests some day, but in the mean time, they're a useful sanity
check for future changes.)
|
| |
|
|
|
|
| |
that it always returns the same nonzero value.
|
| |
|
| |
|
| |
|
|
|
|
| |
versions in libm, not the gcc builtins.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I wrote these to test amd64 asm functions that used
maxss, maxsd, minss, and minsd, but it turns out that
those instructions don't handle NaNs and signed zero
in the same way as fmin() and fmax() are required to,
so we're stuck with the C versions for now.
|
| |
|
| |
|
| |
|
|
|
|
| |
precision.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
mostly just test corner cases rather than accuracy. Some of the
tests don't pass right now if you compile libm at -O2 due to gcc
constant-folding some things that it shouldn't. I'll fix that
shortly.
|
|
|
|
|
| |
tailored for the long double format; instead, I just modified the existing
tests to test lrintl() and llrintl() as well.
|
|
|
|
| |
can cause them to fail.
|