| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This test seems to work even with "x87" floating point; perhaps it fails
on, e.g., SPARC with some compiler.
|
| |
|
|
|
|
|
|
|
| |
Add a --fp-type flag to tcpdump, which causes it to do a floating-point
operation and, based on the result of the operation, prints out
"FPTYPE{n}", where {n} is a number indicating the result.
Have tests/TESTrun run "./tcpdump --fp-type" and set a HAVE_ key based
on that. Run some tests only for FPTYPE1.
|
| |
|
|
|
|
|
|
|
|
|
| |
I can't seem to make those issues pop up on my (x86-64) machine, and, if
they do show up on any platforms, the best hack to handle it is probably
to have a special tcpdump flag to force it to do a floating-point
calculation and see what result is generated, and report the result, so
we know what it'll do with the numbers in the test files, and have
tests/TESTrun run tcpdump with that flag.
If those tests *do* fail, we'll know what calculations to do.
|
| |
|
|
|
|
|
|
|
| |
Remove a stray .md file and restore some comments from the removed .sh
files so future folk can see where the conditional tests come from, not
just the mere fact of their existence. Remove the unused fragile shebang
from testfuncs.pm.
[skip ci]
|
| |
|
