| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
- Replace magic 14 with PIL_TICK.
|
|
|
|
|
|
|
| |
is not performance critical code anyway. Also, avoid using strlen() to
obtain information which we already have.
MFC after: 3 weeks
|
|
|
|
| |
Submitted by: Bård Skaflestad <bardsk@math.ntnu.no>
|
|
|
|
| |
that I make stupid fundamental mistakes like this when I don't.
|
| |
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
|
| |
flopen(3) function which reliably opens and locks a file.
MFC after: 3 weeks
|
|
|
|
|
|
|
| |
and its bibliography.
Submitted by: Tomoyuki Okazaki <okazaki at kick dot gr dot jp>
MFC after: 1 month
|
| |
|
|
|
|
|
|
| |
PR: kern/112515
Submitted by: Ryan C. Gordon <icculus@icculus.org>
MFC after: 3 weeks
|
|
|
|
| |
even if the programmer asks for zero padding.
|
|
|
|
| |
Reported by: Bruno Haible
|
| |
|
|
|
|
|
|
| |
with GEOM providers.
OK'ed by: phk
|
|
|
|
|
| |
Approved by: keramida (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that ints have >= 31 value bits elsewhere. s/int/int32_t/ seems to
have been done too globally for all other files in msun/src before
msun/ was imported into FreeBSD.
Minor fixes in comments.
e_lgamma_r.c:
Describe special cases in more detail:
- exception for lgamma(0) and lgamma(neg.integer)
- lgamma(-Inf) = Inf. This is wrong but is required by C99 Annex F. I
hope to change this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(1) tgamma(-Inf) returned +Inf and failed to raise any exception, but
should always have raised an exception, and should behave like
tgamma(negative integer).
(2) tgamma(negative integer) returned +Inf and raised divide-by-zero,
but should return NaN and raise "invalid" on any IEEEish system.
(3) About half of the 2**52 negative intgers between -2**53 and -2**52
were misclassified as non-integers by using floor(x + 0.5) to round
to nearest, so tgamma(x) was wrong (+-0 instead of +Inf and now NaN)
on these args. The floor() expression is hard to use since rounding
of (x + 0.5) may give x or x + 1, depending on |x| and the current
rounding mode. The fixed version uses ceil(x) to classify x before
operating on x and ends up being more efficient since ceil(x) is
needed anyway.
(4) On at least the problematic args in (3), tgamma() raised a spurious
inexact.
(5) tgamma(large positive) raised divide-by-zero but should raise overflow.
(6) tgamma(+Inf) raised divide-by-zero but should not raise any exception.
(7) Raise inexact for tiny |x| in a way that has some chance of not being
optimized away.
The fix for (5) and (6), and probably for (2), also prevents -O optimizing
away the exception.
PR: 112180 (2)
Standards: Annex F in C99 (IEC 60559 binding) requires (1), (2) and (6).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
values in more detail, and change the style of this comment to be closer
to fdlibm and C99:
- tgamma(-Inf) was undocumented and is wrong (+Inf, should be NaN)
- tgamma(negative integer) is as intended (+Inf) but not best for IEEE-754
(NaN)
- tgamma(-0) was documented as being wrong (+Inf) but was correct (-Inf)
- documentation of setting of exceptions (overflow, etc.) was more
complete here than in most of libm, but was further from matching
the actual setting than in most of libm, due to various bugs here
(primarily, always evaluating +Inf one/zero and getting unwanted
divide-by-zero exceptions from this). Now the actual behaviour with
gcc -O0 is documented. Optimization still breaks setting of exceptions
all over libm, so nothing can depend on this working.
- tgamma(NaN)'s exception was documented as being wrong (invalid) but was
correct (no exception with IEEEish NaNs).
Finish (?) rev.1.5. gamma was not renamed to tgamma in one place.
Finish (?) rev.1.6. errno.h was not completely removed.
|
|
|
|
|
|
|
| |
This is a no-op as far as FreeBSD is concerned, but makes libarchive
more autoconf-friendly.
Approved by: kientzle
|
|
|
|
| |
Tested with: md5(1)
|
| |
|
|
|
|
|
|
|
|
|
| |
Not because I admit they are technically wrong and not because of bug
reports (I receive nothing). But because I surprisingly meets so
strong opposition and resistance so lost any desire to continue that.
Anyone who interested in POSIX can dig out what changes and how
through cvs diffs.
|
|
|
|
|
|
|
|
|
|
|
| |
needed to hold the GEOM tree. At this point, pointer 'p' has an improper
value (as it was used previously), and we're getting EFAULT. Fix this
functionality by passing NULL instead of 'p'.
This fixes mdconfig(8) -l output with high number of md(4) devices.
Found by: kris
Reviewed by: phk
|
|
|
|
| |
Suggested by: Henrik Brix Andersen <henrik@brixandersen.dk>
|
|
|
|
|
| |
"so altering the argument shall change the environment."
into putenv description.
|
|
|
|
|
|
|
|
|
|
|
| |
(also IEEE Std 1003.1-2001)
The specs explicitly says that altering passed string
should change the environment, i.e. putenv() directly puts its arg
into environment (unlike setenv() which just copies it there).
It means that putenv() can't be implemented via setenv()
(like we have before) at all. Putenv() value lives (allows modifying)
up to the next putenv() or setenv() call.
|
|
|
|
|
|
|
|
|
| |
compatibility with the different environment conventions" (man page).
With the standards, we don't have them different anymore and
IEEE Std 1003.1-2001 says that
"The values that the environment variables may be assigned are not
restricted except that they are considered to end with a null byte"
|
|
|
|
|
|
|
|
|
| |
Issue 6 (also IEEE Std 1003.1-2001) in following areas:
args, return, errors.
Putenv still needs rewriting because specs explicitly says that
altering passed string later should change the environment (currently we
copy the string so can't provide that).
|
| |
|
| |
|
|
|
|
| |
inheritance chain.
|
| |
|
| |
|
|
|
|
| |
compatibility between versions (as we do for the public namespace).
|
| |
|
|
|
|
|
|
|
|
| |
it is only relevant to receiving data from sockets, not to sending.
PR: 109667
Submitted by: Jari Kirma <kirma@cs.hut.fi>
Approved by: wollman
|
|
|
|
|
|
| |
Why would an XML library need to know about endianess anyway ??
Prodded by, long time ago: ahze
|
|
|
|
| |
Obtained from: TrustedBSD Project
|
|
|
|
| |
Submitted by: davidxu (via libthr)
|
|
|
|
|
|
|
|
|
|
| |
once (CWD a/b/c vs. 3 CWDs). If an error occurs, we fall back to the default
method of a single CWD per directory element. Since this is technically
a violation of the basic FTP RFC, this behavior is under a compile-time
option FTP_COMBINE_CWDS and is off by default. It should work with most
Unix-based FTP daemons and can save latency.
MFC after: 2 weeks
|
|
|
|
| |
Thanks to: VMiklos
|
|
|
|
|
|
|
|
|
|
|
| |
1. CMSG_NXTHDR(mhdr, cmsg) is supposed to dereference cmsg and return
the next header in the chain. If cmsg is NULL it should return
the first header, behaving essentially like CMSG_FIRSTHDR().
2. inet6_rth_(space|init|add) should do basic checking on their input
to verify that the number of headers (segments) is
between 0 and 127 inclusive.
MFC-After: 1 month
|
| |
|
|
|
|
| |
don't program against our more restrictive behaviour.
|
| |
|
|
|
|
|
|
|
| |
- Remove link for define_key.3 which is a real man page
- Some whitespace nits
Approved by: delphij (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
occur on the write side of extracting a file to ARCHIVE_WARN errors
when returning them from archive_read_extract.
In bsdtar: Use the return code from archive_read_data_into_fd and
archive_read_extract to determine whether we should continue trying to
extract an archive after one of the entries fails.
This commit makes extracting a truncated tarball complain once about
the archive being truncated, instead of complaining twice (once when
trying to extract an entry, and once when trying to seek to the next
entry).
Discussed with: kientzle
|
| |
|
| |
|